Google Chrome: Memory corruption in CSS engine
Summary
Google Chrome versions before 156.0.8078.47 contain a memory corruption flaw in the CSS engine (CWE-119). A remote attacker can use a crafted HTML page to potentially execute arbitrary code outside the browser sandbox. Exploitation requires that a user visits the page, for example through a link in a phishing email. Google rates the issue Critical; no public exploit and no known exploitation have been reported.
Affected
- Google Chrome desktop for Linux: before 156.0.8078.47
- Google Chrome desktop for Windows and macOS: before 156.0.8078.47 or 156.0.8078.48 (third-party summary, not verified against the vendor)
- Google Chrome for Android: before 156.0.8078.47 (third-party summary)
- Google Chrome for iOS: Unknown (sources conflict)
Fixed in
- Desktop Linux: 156.0.8078.47
- Desktop Windows and macOS: 156.0.8078.47 or 156.0.8078.48 (third-party summary)
- Android: 156.0.8078.47 (third-party summary)
- iOS: Unknown
Workaround
- Unknown. No separate mitigation was found.
- Install the fixed build and restart Chrome, because the update only takes effect after a relaunch.
Exploitation
- No known exploitation reported.
- Not listed in the CISA KEV catalog according to an automated alert; verify directly.
- No public proof-of-concept found.
- CISA SSVC: exploitation none, not automatable, total technical impact.
Our recommendation
- Update Chrome to version 156.0.8078.47 or later on all endpoints and restart the browser.
- Check managed devices for outdated Chrome versions and check other Chromium-based browsers, such as Edge, for their own updates.
- Treat this as urgent and remind users not to open unknown links.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Google Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker issues.chromium.org
- NVD record via Vulners vulners.com
- NVD detail (referenced in research notes) vulners.com
- Chrome 156 security update summary (Penligent) www.penligent.ai
- Chrome 156 security notice (TechGeeks) www.techgeeks.org
- Chrome 156 security update (WindowsForum) windowsforum.com
- Chrome security update fixing 353 flaws (Cybersecurity News) cybersecuritynews.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 30 Oct 2026, 22:37.
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 outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
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.