Google Chrome: Use After Free in the V8 JavaScript engine
Summary
A use-after-free flaw in the V8 JavaScript engine of Google Chrome allows a remote attacker to execute arbitrary code inside the browser sandbox. The attack requires a user to visit a crafted HTML page, so no login or internet-exposed service is needed. Google rates the issue High, and a full compromise of the system would still need a further sandbox escape, which is not described in the available sources.
Affected
- Google Chrome desktop builds (Windows, macOS, Linux) prior to 155.0.8059.84
- Other Chromium-based browsers (for example Edge, Brave, Opera) until their own builds include the fix
Fixed in
- Windows and macOS: Chrome 155.0.8059.84 or higher (Google lists .84 and .85; use .85 where offered)
- Linux: Chrome 155.0.8059.84
- Android: Chrome 155.0.8059.84 (available on Google Play over the following days)
- Debian 12 and 13: chromium 156.0.8078.47 (verify against the distribution tracker)
- Ubuntu: update Chromium through the snap channel
Workaround
- Unknown. The vendor provides no workaround; updating is the only fix.
Exploitation
- No known exploitation in the wild according to Google and the reviewed reports.
- Not listed in the CISA KEV catalog.
- CISA SSVC assessment (CISA ADP): exploitation none, automatable no.
- No public proof of concept found; Google has not published technical details.
Our recommendation
- Update Google Chrome and all other Chromium-based browsers on all endpoints to the fixed versions above, and check the installed version.
- Make sure browsers are restarted after the update, since the fix is not active before that.
- Use central management (for example Chrome Enterprise policies or an endpoint management tool) to verify the rollout.
- Treat this as a medium-high priority because browser zero-days are common and the fix requires no cost.
- Monitor vendor advisories for exploitation reports.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker 569286602 issues.chromium.org
- OpenCVE: CVE-2026-110921 app.opencve.io
- Ubuntu Security: CVE-2026-110921 ubuntu.com
- Vulners Debian CVE: CVE-2026-110921 vulners.com
- Cybersecurity News: Google fixes 10 Chrome vulnerabilities cybersecuritynews.com
- SecurityOnline: Chrome security update 155.0.8059.84 securityonline.info
- Chrome Geek: Chrome 155 stable security update www.chromegeek.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 16:12.
Original description (NVD)
Use after free in V8 in Google Chrome prior to 155.0.8059.84 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.