HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2026-11645

Google Chromium V8 Out-of-Bounds Read and Write Vulnerability

Google Chromium V8

Out of bounds read and write in V8 in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
2.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
9 Jun 2026
CWE-125, CWE-787

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 9 June 2026. US federal agencies were required to remediate it by 23 June 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 2.2%, which is higher than 80.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2026-11645 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2026-11645.

What does CVE-2026-11645 affect?

CVE-2026-11645 affects Google Chromium V8. Out of bounds read and write in V8 in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2026-11645?

CVE-2026-11645 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 2.2%, higher than 80.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 June 2026.

How should organisations respond to CVE-2026-11645?

Apply the vendor patch for Google Chromium V8 as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.