Google Chrome: Use-after-free in Extensions component allows sandbox code execution
Summary
A use-after-free vulnerability (CWE-416) in the Extensions component of Google Chrome allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs the victim to load a crafted HTML page, and no privileges are required. The advisory does not describe a sandbox escape, so full system compromise is not confirmed. Google rates the issue Medium, while NVD scores it 8.8 (High).
Affected
- Google Chrome versions before 156.0.8078.47 (per the CVE description)
- The CVE record gives an inconsistent range; VulDB lists affected versions up to 155.0.8059.84
- Chromium-based products such as Microsoft Edge are affected until they ingest the Chromium fix
Fixed in
- Google Chrome 156.0.8078.47 (Linux) or 156.0.8078.48 (Windows and Mac, per Wikipedia)
- Deploy the current Stable build of Chrome, as later builds are newer than the fix
- Ubuntu: check the Chromium snap version, not the chromium-browser deb package
Workaround
Unknown. No vendor-published workaround found.
- Interim measures (recommendations, not from the vendor): keep auto-update enabled and restart the browser after updates
- Remove unneeded extensions and keep the remaining ones current
- On managed fleets, restrict extension installation by policy
Exploitation
- No evidence of exploitation in the wild found
- Not listed in CISA KEV according to a tracker
- No public proof of concept found
- EPSS score: unknown
- CISA SSVC: exploitation none, automatable no, technical impact total
Our recommendation
- Update Google Chrome to the current Stable build on all endpoints, including remote and home-office devices, and verify the installed version
- Restart the browser after the update so the new version is active
- Patch the whole browser release, as the update contains other vulnerabilities
- Use the NVD score of 8.8 for risk ranking, as Google rates the issue lower
- Restrict extension installation and remove unneeded extensions
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 517486906 issues.chromium.org
- VulDB CVE entry 424167 vuldb.com
- Vulners CVE record vulners.com
- Ubuntu security tracker CVE-2026-113042 ubuntu.com
- BrowserHow Chrome 156 stable update browserhow.com
- Google Chrome on Wikipedia en.wikipedia.org
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:41.
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.