Google Chrome: Memory corruption in V8 JavaScript engine
Summary
Google Chrome contains a memory corruption flaw in the V8 JavaScript engine, classified as CWE-119. A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. The victim must visit the page, and the description does not say whether a sandbox escape exists for full compromise.
Affected
- Google Chrome prior to 156.0.8078.47 (per the CVE description).
- Chromium-based browsers that include the affected V8 code, such as Microsoft Edge, Brave or Vivaldi, should be checked against their own vendor advisories.
- Linux distributions: Debian chromium (DSA 6577-1, DLA 4853-1). Ubuntu delivers Chromium through the snap package.
Fixed in
- Chrome 156.0.8078.47 or later per the Chrome Releases post of 20 October 2026 (version numbers from secondary reporting, to be verified).
- Later Stable builds 156.0.8078.79 or later, according to a secondary report of a 29 October 2026 update (not verified against the vendor blog).
- Debian and Ubuntu: fixed packages are listed in the respective security notices.
Workaround
- No vendor workaround known. Installing the update is the fix.
Exploitation
- CISA SSVC assessment in the official CVE record: exploitation none, automatable no, technical impact total.
- No evidence of active exploitation found in the sources reviewed.
- No public proof of concept found.
- Not verified: CISA KEV listing.
Our recommendation
- Confirm that all Chrome and Chromium-based browsers, including Linux and Ubuntu snap installs, run 156.0.8078.79 or later.
- Verify that managed devices have restarted after the update.
- Prioritise this update, as Chrome 156 fixes further security issues in the same release.
- Monitor vendor advisories for exploitation status changes.
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
- Ubuntu security tracker: CVE-2026-113052 ubuntu.com
- Vulners: CVE-2026-113052 (NVD mirror) vulners.com
- Vulners: CVELIST record CVE-2026-113052 vulners.com
- ChromeGeek: Chrome 156 security update fixes 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, 14:35.
Original description (NVD)
Memory corruption in V8 in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
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.