Google Chrome: Memory corruption in DevTools allows code execution
Summary
Memory corruption in the DevTools component of Google Chrome allows a remote attacker to execute arbitrary code outside the browser sandbox. The attacker only needs to lure a user to a crafted HTML page, so no login is required. NVD rates the issue 9.6 (Critical), while VulDB rates it 6.3 (Medium); the official score should be confirmed on NVD.
Affected
- Google Chrome desktop builds prior to 156.0.8078.47
- Linux: before 156.0.8078.47
- Windows and macOS: before 156.0.8078.47 or 156.0.8078.48 (sources differ)
- Android: before 156.0.8078.47 (according to secondary sources)
- Ubuntu chromium-browser package: not affected; the Chromium snap is affected
Fixed in
- Chrome 156.0.8078.47 for Linux
- Chrome 156.0.8078.47 or 156.0.8078.48 for Windows and macOS
- Latest Chrome 156 stable build recommended, as it includes this fix
Workaround
- No vendor-documented workaround. Updating Chrome is the fix.
- Restart the browser after the update, because an old browser process may still run.
- Disabling DevTools is a possible hardening step, but it is not confirmed by a source.
Exploitation
- No evidence of exploitation in the wild found at the time of writing.
- No public proof-of-concept or exploit known (VulDB).
- Not listed in CISA KEV according to a GitHub alert; the KEV catalogue was not checked directly.
- Chromium rates the bug Low, the CVSS score is disputed.
Our recommendation
- Inventory Chrome versions on all endpoints, including Linux, Android and Ubuntu snap installs.
- Update Chrome to the latest 156 stable build and restart the browser.
- Ensure managed devices receive updates and are not stuck on old builds.
- Recheck NVD and CISA KEV in a few days, as severity and exploitation status may change.
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 CVE-2026-113186 ubuntu.com
- Vulners CVE-2026-113186 vulners.com
- VulDB entry 424540 vuldb.com
- Strix CVE-2026-113186 www.strix.ai
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- Penligent: Chrome 156 security update www.penligent.ai
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 30 Oct 2026, 22:31.
Original description (NVD)
Memory corruption in DevTools in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)
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.