Google Chromium V8: vulnerability flaw under attack

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 contains an out of bounds write vulnerability that allows a remote attacker to execute arbitrary code inside the 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 vulnerability flaw. It lets an attacker misuse the product in a way its maker did not intend. CISA lists it because attackers are confirmed to be using it against real systems.

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

1. 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.
2. Turn on automatic updates so the next fix arrives without you having to look for it.
3. If your device is too old to receive this update, stop using the affected app for anything sensitive and plan a replacement.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Vendor advisories and fixes

• chromereleases.googleblog.comchromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on September 9, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by September 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 3.1% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 88% 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 write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)