Secuno
ENNL
Book demo

CVE-2026-85053

8.8 HIGHEPSS 0.29%
  1. Published3 Sept 2026

Description

Improper resource exposure in CacheStorage in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Google Chrome< 152.0.7977.82

Remediation

Fixed in
Google Chrome≥ 152.0.7977.82

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-9294010.0
vm2 versions 3.11.3 through 3.11.6 expose the host process's real https.globalAgent to…
CVE-2026-738439.6
OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.2…
CVE-2026-674278.6
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to…
CVE-2026-547278.2
proot-distro is a utility for managing proot containers. Prior to version 5.1.6,…
CVE-2026-149609.8
Pegatron `Tdelo64.sys` improperly exposes privileged hardware access functionality…
CVE-2026-450778.6
Symfony is a PHP framework for web and console applications and a set of reusable PHP…

Frequently asked

Is CVE-2026-85053 being actively exploited?

CVE-2026-85053 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.29%.

How severe is CVE-2026-85053?

CVE-2026-85053 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.29% probability of exploitation.

Which products are affected by CVE-2026-85053?

Affected products include Google Chrome.

How do I fix CVE-2026-85053?

Upgrade affected software to a fixed version, for example Google Chrome 152.0.7977.82 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-85053 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.