Google Chrome: Memory corruption in CSS enables code execution in sandbox
Summary
Google Chrome desktop versions before 156.0.8078.47 contain a memory corruption bug in CSS handling. A remote attacker may be able to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Exploitation requires user interaction, such as opening a malicious link, and the sources describe no sandbox escape. Chromium-based browsers may inherit the bug.
Affected
- Google Chrome desktop (Windows, macOS, Linux) prior to 156.0.8078.47
- Chromium-based browsers that include the affected Chromium code
- Note: the affected range in the CVE record is inconsistent (156.0.8078.47 to < 156.0.8078.47); VulDB lists up to 155.0.8059.84
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux)
- Windows and macOS: 156.0.8078.48 or later (not confirmed in the vendor post)
- The newest Stable build is recommended; newer Stable builds (reported as 156.0.8078.79 or later) are available
Workaround
No workaround. Install the update and restart the browser so the fix takes effect.
Exploitation
- No evidence of exploitation in the wild found; one tracker lists it as not in CISA KEV, which must be verified directly.
- No public proof-of-concept found in our searches.
- CISA SSVC: exploitation none, not automatable, total technical impact.
- One aggregator lists EPSS 0.00417.
Our recommendation
- Confirm that all Chrome and Edge installations run 156.0.8078.47 or later (Windows/macOS: 156.0.8078.48 or later), ideally the newest 156.x build.
- Ensure browsers are fully restarted after updating.
- Enforce updates on managed and BYOD devices through your management tooling.
- Check other Chromium-based or embedded browser products supplied by vendors.
- Re-check CISA KEV and the Chromium bug for status changes.
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 560664595 issues.chromium.org
- Microsoft Security Update Guide: CVE-2026-112997 msrc.microsoft.com
- VulDB entry 423060 vuldb.com
- Vulners CVE list entry vulners.com
- GitHub CVE tracker issue 2646 github.com
- TechSpot Google Chrome download page www.techspot.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, 15:05.
Original description (NVD)
Memory corruption in CSS in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially 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.