Google Chrome: Use-after-free in Core component allows code execution in sandbox
Summary
A use-after-free memory flaw in the Core component of Google Chrome 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, so no authentication is required but user interaction is. Full compromise normally requires an additional sandbox escape, and the CVE's linked Chromium bug does not match the description, so the exact scope is still being verified.
Affected
- Google Chrome before 156.0.8078.47 (per the CNA description)
- VulDB lists the affected range as up to 155.0.8059.84
- The official CNA record shows an inconsistent range (156.0.8078.47 to < 156.0.8078.47), so verify against the Chrome advisory and NVD
- Microsoft Edge before 156.0.4314.42 (third-party HKCERT bulletin)
Fixed in
- Google Chrome 156.0.8078.47 or later for Desktop (Linux, Windows, Mac)
- Third-party sources report later builds (156.0.8078.79 or .80); use the newest stable build from the official channel
- Microsoft Edge 156.0.4314.42 or later
- Ubuntu: check the Snap revision of the Chromium package
Workaround
Unknown. No vendor-documented mitigation was found. Applying the update is the only confirmed fix.
Exploitation
- No evidence of in-the-wild exploitation found; no CISA KEV entry identified in the research (manual check recommended)
- No public proof-of-concept found
- CISA SSVC: exploitation none, automatable no, technical impact total
- VulDB estimates an exploit price of USD 5,000 to 25,000; this is a price estimate, not evidence of use
Our recommendation
- Update Google Chrome and Microsoft Edge to the newest stable build on all desktops immediately
- Check the browser version across the fleet, not only the first fixed build
- Enforce automatic browser updates and review update policies in managed environments
- Monitor the official Chrome release notes and CISA KEV 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 (linked from CVE, verify mapping) issues.chromium.org
- VulDB entry vuldb.com
- Vulners CVE record (CNA text mirror) vulners.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Ubuntu security tracker ubuntu.com
- Browserhow Chrome 156 stable update guide (third-party) browserhow.com
- Strix CVE record 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:01.
Original description (NVD)
Use after free in Core 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.