Google Chrome: Use after free in V8 JavaScript engine allows code execution
Summary
Google Chrome versions before 155.0.8059.79 contain a use-after-free vulnerability in the V8 JavaScript engine. A remote attacker can execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Exploitation requires the user to visit the malicious page; a full compromise of the system would require an additional sandbox escape, which is not described in the record.
Affected
- Google Chrome prior to 155.0.8059.79
- Chromium-based browsers using the same V8 engine have not been verified and need their own updates
Fixed in
- Google Chrome 155.0.8059.79 (Windows and Linux) and 155.0.8059.79/.80 (Windows and Mac), Stable channel update of 13 October 2026
- Debian bookworm: 155.0.8059.79-1~deb12u1
- Ubuntu: chromium-browser packages are listed as not affected; the Chromium snap is updated separately
- Install the current stable build, as newer Chrome 156 releases are already available
Workaround
- Unknown. No workaround is documented; updating Chrome is the required step.
Exploitation
- No evidence of in-the-wild exploitation found; this could not be confirmed as a negative.
- CISA KEV status: not confirmed by a primary source.
- No public proof-of-concept found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Google Chrome to the current stable version on all workstations and restart the browser.
- Verify the installed version on managed endpoints, since rollout is staged and a manual check via About Google Chrome may be needed.
- Update Chromium-based browsers such as Edge or Brave separately and check their advisories.
- Treat this as a high priority within the normal emergency patch window, as browsers are exposed to web content by design.
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 entry issues.chromium.org
- Debian OSV entry osv.dev
- Ubuntu security notice ubuntu.com
- Malwarebytes: Chrome fixes 37 security flaws www.malwarebytes.com
- CISA Known Exploited Vulnerabilities would need checking github.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, 17:01.
Original description (NVD)
Use after free in V8 in Google Chrome prior to 155.0.8059.79 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.