Google Chrome: Use-after-free in CSS allows code execution in sandbox
Summary
Google Chrome versions before 156.0.8078.47 contain a use-after-free flaw in the CSS engine (CVE-2026-113203, CWE-416). A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. The attack requires that a user visits the malicious page, and no privileges are needed. Google rates the flaw Medium; NVD and MSRC score it CVSS 8.8.
Affected
- Google Chrome prior to 156.0.8078.47 (desktop)
- Other Chromium-based browsers that include the affected Chromium code, such as Microsoft Edge (HKCERT lists Edge versions before 156.0.4314.42)
- Exact affected Android and Linux builds: see the Chrome Releases advisory
Fixed in
- Chrome 156.0.8078.47 or later (Linux, per Wikipedia and coverage)
- Chrome 156.0.8078.47 or 156.0.8078.48 or later (Windows and macOS; sources differ, verify on the Chrome Releases page)
- Microsoft Edge 156.0.4314.42 or later (per HKCERT)
- Debian and Ubuntu fixed package versions: Unknown.
Workaround
- None needed if Chrome is updated.
- Mitigation for unpatched Chromium forks: Unknown.
Exploitation
- No evidence found that this CVE is exploited in the wild.
- Not listed in CISA KEV according to Strix (not independently verified).
- CISA SSVC: exploitation none, automatable no, technical impact total.
- No public proof of concept found.
- Do not confuse with CVE-2026-2441, a different Chrome CSS use-after-free that is confirmed exploited and listed in CISA KEV.
Our recommendation
- Confirm that all Chrome, Edge and other Chromium browsers on managed devices run a fixed build.
- Enforce a browser restart after updates, because an old process may still run after the update.
- Check Linux and Android fleets separately, since the fixed versions differ by platform.
- Verify the release date and fixed versions on the Chrome Releases page before rollout.
- Monitor for exploitation news and check CISA KEV for 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 tracker issues.chromium.org
- Microsoft Security Update Guide: CVE-2026-113203 msrc.microsoft.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Ubuntu CVE tracker: CVE-2026-113203 ubuntu.com
- Vulners: CVE-2026-113203 (CVELIST) vulners.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- Strix: CVE-2026-113203 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, 13:03.
Original description (NVD)
Use after free 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.