Actively exploited vulnerability
Google Chromium V8: information disclosure flaw under attack
CVE-2026-11645 · Google Chromium V8 Out-of-Bounds Read and Write Vulnerability
What is affected
Google Chromium V8 is found on ordinary personal computers and phones, so this is not only a problem for companies. If you use it and have not updated since the fix was released, you are exposed.
Google Chromium V8 out-of-bounds read and write vulnerability that could allow a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
What an attacker can do
This is a information disclosure flaw. It lets an attacker read data they are not supposed to see, such as memory contents, credentials or internal files. It is often the first step of a larger attack.
- How it is reached
- Over the internet or network
- Access the attacker needs
- No account needed
- Does the victim have to do something?
- Yes, the victim must open or click something
What to do
- Update Google Chromium V8 now. Open the update or "About" screen, install whatever is offered and restart the app or device, because the fix is not active until you do.
- Turn on automatic updates so the next fix arrives without you having to look for it.
- If your device is too old to receive this update, stop using the affected app for anything sensitive and plan a replacement.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor advisories and fixes
- chromereleases.googleblog.comchromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html
- issues.chromium.orgissues.chromium.org/issues/506689381
How urgent is it
CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on June 9, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by June 23, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.
The EPSS model estimates a 2.4% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 84% of all scored vulnerabilities.
Its CVSS severity score is 8.8 out of 10 (high), as recorded in the US National Vulnerability Database.
Technical description
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)