Google Chrome: Use after free in Extensions
Summary
A use-after-free flaw in the Extensions component of Google Chrome before 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the sandbox. The attacker needs a victim to open a crafted HTML page, so user interaction is required. Because the code runs inside the sandbox, a full compromise may require an additional sandbox escape, which is an inference and not a vendor statement.
Affected
- Google Chrome prior to 156.0.8078.47
- Chromium-based browsers that ingest the fix, such as Microsoft Edge, depend on their own vendor advisories
- Linux Chromium packages (Snap or distribution packages): status varies, Ubuntu lists chromium-browser as not affected because it is a Snap wrapper, Debian package versions unknown
Fixed in
- Google Chrome 156.0.8078.47 or later (Windows and macOS builds are listed as 156.0.8078.48)
- Latest Chrome Stable build recommended, as later Chrome 156 builds (for example 156.0.8078.73 and 156.0.8078.79) fix other vulnerabilities
- Microsoft Edge 156.0.4314.42 or later per a secondary advisory (not verified against MSRC)
- Debian DSA 6577-1 and DLA 4853-1 issued, exact package versions unknown
Workaround
Unknown. No vendor workaround is documented because a patch is available. General hardening such as enforcing auto-updates and allowing only approved extensions reduces risk but is not a documented fix.
Exploitation
- CISA SSVC: exploitation none, not automatable, technical impact total
- No public proof of concept or in-the-wild exploitation found in the research
- Not verified against the CISA KEV catalog
- Chromium severity: Medium; CVSS 3.1 base score 8.8; EPSS 0.00443
Our recommendation
- Update all managed Chrome and Chromium-based browsers (including Edge) to the latest Stable build now
- Verify versions on all endpoints and prioritise unmanaged workstations
- Check Linux Chromium Snap or distribution packages
- Enforce automatic updates and restrict installation of untrusted browser extensions
- Make sure staff are aware of phishing and malicious website risks
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
- CVE record (Vulners CVELIST) vulners.com
- Ubuntu security notice CVE-2026-113174 ubuntu.com
- Microsoft Edge advisory (HKCERT) www.hkcert.org
- Google Chrome version context (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, 13:15.
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.