Google Chrome: Use-after-free in Extensions enables code execution in sandbox
Summary
A use-after-free flaw in the Extensions component of desktop Google Chrome before 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs only to lure a user to a crafted HTML page, and no login is required. Per the description, the impact is limited to the sandbox, so a full compromise would normally also need a sandbox-escape flaw. CISA SSVC rates exploitation as none and automatable as no.
Affected
- Google Chrome desktop before 156.0.8078.47 (Linux)
- Google Chrome desktop before 156.0.8078.47 or 156.0.8078.48 (Windows and macOS, according to secondary sources; not verified against the vendor advisory)
- Microsoft Edge before 156.0.4314.42 (separate product, according to HK CERT)
- Ubuntu chromium-browser package: not affected, because it installs the Chromium snap
Fixed in
- Google Chrome 156.0.8078.47 (Linux)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 (Windows and macOS, according to secondary sources)
- Microsoft Edge 156.0.4314.42 or later
- Any current Chrome stable build includes the fix
Workaround
- Unknown. No vendor-stated workaround is available for unpatched systems.
- Interim measure (not from a source): allow only approved browser extensions and remove unused ones.
Exploitation
- Unknown. No in-the-wild exploitation, public proof of concept or CISA KEV listing was found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Google Chrome to the latest stable build and restart the browser, because a pending update takes no effect until restart.
- Update Microsoft Edge through its own channel.
- On Linux, refresh the Chromium snap on Ubuntu and apply the Debian DSA/DLA updates for Chromium.
- Check that automatic browser updates work on all managed devices, including laptops used from home.
- Restrict browser extensions to an approved list and remove unused ones.
- Monitor the CISA KEV catalogue and the vendor advisory for 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 495899355 issues.chromium.org
- HK CERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Vulners: CVE-2026-113113 vulners.com
- Ubuntu security: CVE-2026-113113 ubuntu.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- TechGeeks: Security notice Google Chrome 156 stable www.techgeeks.org
- Windows Forum: Chrome 156 security update windowsforum.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:54.
Original description (NVD)
Use after free 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.