Google Chrome: Memory corruption in DevTools allows code execution in sandbox
Summary
A memory corruption flaw in the DevTools component of Google Chrome allows a remote attacker to execute arbitrary code inside the browser's renderer sandbox. Exploitation requires that a user visits a crafted HTML page, for example through a phishing link or a malicious website. Code execution inside the sandbox is usually only one step; a further flaw is needed to escape it and fully compromise the system. Chromium rates the issue Medium.
Affected
- Google Chrome desktop builds prior to 156.0.8078.47 (CVE description)
- Linux builds prior to 156.0.8078.47; Windows and macOS builds reported as .47 or .48 by secondary sources (unverified against the vendor post)
- Android builds prior to 156.0.8078.47 (secondary sources)
- Microsoft Edge prior to 156.0.4314.42 (HKCERT)
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux); Windows and macOS: 156.0.8078.48 or later according to secondary sources, to be checked against the vendor post
- Use the latest stable build, as later Chrome 156 builds also contain fixes
- Microsoft Edge 156.0.4314.42 or later
- Linux: Debian DSA 6577-1 and DLA 4853-1 for Chromium; on Ubuntu, update the Chromium snap (the chromium-browser package is not affected)
Workaround
Unknown. No vendor-documented workaround found.
- Interim option, not verified for this CVE: restrict DevTools via the enterprise policy DeveloperToolsAvailability and avoid untrusted sites until patched.
Exploitation
Unknown. No in-the-wild exploitation, CISA KEV entry or public proof of concept found for this CVE. CISA SSVC: exploitation none, automatable no, technical impact total.
Our recommendation
- Update Chrome and Edge to the latest stable build and restart the browser, as updates only take effect after a relaunch.
- Verify the installed versions on all endpoints, including Edge and Linux snap installs.
- Make sure automatic updates work.
- Until patched, restrict access to untrusted sites and warn users about suspicious links.
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 553114456 issues.chromium.org
- Vulners: CVE-2026-113136 (CVE list) vulners.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Ubuntu: CVE-2026-113136 ubuntu.com
- TechGeeks: Google Chrome 156 stable security notice www.techgeeks.org
- Vuldb: vulnerability 424164 (related DevTools CVE) vuldb.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, 13:45.
Original description (NVD)
Memory corruption in DevTools 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.