Google Chrome: Memory corruption in Browser allows code execution in sandbox
Summary
A memory corruption flaw in the Browser component of Google Chrome before 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the browser sandbox. The attack requires a user to visit a crafted HTML page. NVD rates the issue 8.8 (High), while Google rates it Low. The description does not claim a sandbox escape.
Affected
- Google Chrome desktop versions prior to 156.0.8078.47 (CVE description)
- Third-party sources report Android builds before 156.0.8078.47 as affected (not verified against the vendor advisory)
- VulDB lists a different range (up to 155.0.8059.84), which conflicts with the vendor wording
Fixed in
- Linux: 156.0.8078.47 or later
- Windows and macOS: 156.0.8078.47/.48 or later (according to secondary sources; vendor advisory not read directly)
- Android: 156.0.8078.47 or later (according to secondary sources)
Workaround
- No vendor-documented workaround. Installing the update is the fix.
- Restart the browser after the update, because the old process may keep running.
Exploitation
- No evidence of exploitation in the wild found.
- Not listed in CISA KEV according to a third-party tracker; check the KEV catalogue directly.
- No public proof of concept found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Inventory all Chrome and Chromium-based browsers (for example Edge) and their versions.
- Confirm desktop builds are at least 156.0.8078.47 (Linux) or 156.0.8078.47/.48 (Windows/macOS), and mobile builds at 156.0.8078.47 or later.
- Require a browser restart on managed endpoints.
- Treat this as high priority for SME workstations because no login is needed; re-check the vendor advisory and CISA KEV for changes.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- CVE record (mirror) vulners.com
- Chrome Releases: Stable Channel Update for Desktop (vendor advisory) chromereleases.googleblog.com
- Chromium issue tracker issues.chromium.org
- Ubuntu security tracker ubuntu.com
- VulDB vuldb.com
- Release coverage (CybersecurityNews) cybersecuritynews.com
- Release summary (TechGeeks) www.techgeeks.org
- Strix CVE entry 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, 15:13.
Original description (NVD)
Memory corruption in Browser 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: Low)
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.