Google Chrome: Improper input validation in GPU component allows sandbox code execution
Summary
Google Chrome before 156.0.8078.47 contains an improper input validation flaw in the GPU component. A remote attacker can craft an HTML page that may lead to arbitrary code execution inside the browser sandbox. Exploitation requires the victim to visit the malicious page; no privileges are needed.
Affected
- Google Chrome desktop versions before 156.0.8078.47
- Chromium-based browsers that include the same code, such as Microsoft Edge (check their own advisories)
Fixed in
- Google Chrome 156.0.8078.47 or later (Windows and macOS builds 156.0.8078.47 or .48, depending on channel)
- Android: Chrome 156.0.8078.47 reported as fixed
- Debian issued Chromium updates; exact package versions unknown
- Ubuntu chromium-browser package (Snap wrapper) listed as not affected
Workaround
- Unknown. No workaround is documented; updating the browser is the practical mitigation.
Exploitation
- Exploited in the wild: no evidence found.
- Public proof of concept: none found.
- CISA KEV: a third-party tracker reports it is not listed; not verified with CISA.
- CISA SSVC: exploitation none, automatable no, technical impact total.
Our recommendation
- Confirm all desktop and Android Chrome installations are at least 156.0.8078.47.
- Restart the browser after updating, as the update is not complete until then.
- Check Edge and other Chromium-based browsers for their own updates.
- Verify versions via chrome://version or your MDM/update console.
- Patch the whole Chrome 156 release, which contains 353 fixes.
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 msrc.microsoft.com
- Ubuntu security tracker ubuntu.com
- Vulners CVE record (CVELIST) vulners.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.com
- Penligent: Chrome 156 security update www.penligent.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:03.
Original description (NVD)
Improper input validation in GPU 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: High)
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.