Google Chrome: Memory corruption in Extensions allows code execution
Summary
Google Chrome versions before 156.0.8078.47 contain a memory corruption flaw in the Extensions component. A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. Exploitation requires that a user visits the malicious page, and Google rates the Chromium severity as Medium. Microsoft Edge, which is Chromium-based, is also affected according to third-party sources.
Affected
- Google Chrome prior to 156.0.8078.47 (per the CVE description)
- Microsoft Edge prior to 156.0.4314.42 (per HKCERT; check MSRC for the authoritative build)
- Debian chromium packages (DSA 6577-1, DLA 4853-1 list this CVE; package versions not verified)
- Note: the official CVE record's version range is inconsistent ("156.0.8078.47 to < 156.0.8078.47"); the description is used here.
Fixed in
- Google Chrome 156.0.8078.47 (Linux and Android)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 (Windows and macOS, per third-party sources)
- Microsoft Edge 156.0.4314.42 (per HKCERT)
Workaround
Unknown. No vendor-recommended interim mitigation was found; applying the patch is the remedy.
Exploitation
- No evidence of exploitation in the wild found; one summary of the Chrome 156 release states no known exploited bugs.
- No public proof of concept found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Chrome and Edge endpoints to the fixed builds in the normal patch cycle, prioritising internet-facing and unmanaged devices.
- Confirm the running browser version and restart the browser after updating, as old processes may still run.
- Deploy the whole Chrome 156 release, which contains 353 security fixes including six critical ones.
- Monitor vendor advisories for changes in exploitation status.
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 issues.chromium.org
- VulDB 424640 vuldb.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Vulners CVELIST:CVE-2026-113307 vulners.com
- TechGeeks: Security notice Google Chrome 156 stable www.techgeeks.org
- Windowsforum: Chrome 156 security update windowsforum.com
- Strix: CVE-2026-113307 www.strix.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 31 Oct 2026, 12:05.
Original description (NVD)
Memory corruption in Extensions 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.