Google Chrome: Memory corruption in Extensions component
Summary
Google Chrome for desktop (Windows, macOS, Linux) and Android contains a memory corruption flaw in the Extensions component. A remote attacker can potentially read memory inside the browser sandbox by luring a user to a crafted HTML page. Exploitation requires the user to open the page; Google rates the issue Medium and no active exploitation is known.
Affected
- Google Chrome desktop on Linux before 156.0.8078.47
- Google Chrome desktop on Windows and macOS before 156.0.8078.47 or 156.0.8078.48 (vendor data differs by platform)
- Google Chrome for Android before 156.0.8078.47
- Chromium-based browsers that ingest the upstream fix, such as Microsoft Edge (exact fixed build unknown)
Fixed in
- Google Chrome 156.0.8078.47 (Linux, Android)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 (Windows, macOS)
- Debian: DSA 6577-1 and DLA 4853-1 (distribution advisories)
Workaround
- None known. Updating is the only available mitigation.
- Restart the browser after updating, as an old browser process may keep running after the update prompt.
- Unknown whether Google offers a flag-based workaround.
Exploitation
- No known exploitation in the wild. Not listed in CISA KEV at the time of the sources.
- EPSS 0.18% at the time of triage.
- No public proof of concept found.
- Google rates the severity as Medium.
Our recommendation
- Update Google Chrome to 156.0.8078.47 or later on Linux and Android, or to 156.0.8078.47/156.0.8078.48 or later on Windows and macOS.
- Check that Microsoft Edge and other Chromium-based browsers are updated as well.
- Make sure automatic updates are enabled and restart browsers after updating.
- The NVD score is 8.8, while MSRC lists 6.5. Use the NVD score to prioritize.
- Watch CISA KEV and the Chromium bug for status changes. This is part of the standard Chrome 156 update batch.
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
- Microsoft MSRC update guide entry msrc.microsoft.com
- Ubuntu CVE tracker ubuntu.com
- Vulners CVE aggregation vulners.com
- TechGeeks security notice: Google Chrome 156 stable www.techgeeks.org
- Windows Forum: Chrome 156 security update windowsforum.com
- GitHub CVE triage issue (EPSS, KEV status) github.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:46.
Original description (NVD)
Memory corruption in Extensions in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory 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.