Google Chrome: Memory corruption in GPU component allows sandbox code execution
Summary
A memory corruption flaw in the GPU component of Google Chrome allows a remote attacker to execute arbitrary code inside the browser's sandbox. The attack requires that a user visits a crafted HTML page, and no login is needed. A full compromise would additionally require a sandbox escape, which is not described in the available data.
Affected
- Google Chrome prior to 156.0.8078.47
- Affected CNA range as listed: 156.0.8078.47 to < 156.0.8078.47
- Linux distributions: Debian issued DSA 6577-1 and DLA 4853-1 for Chromium; Ubuntu lists its chromium-browser package as not affected (Chromium snap installed)
- Microsoft Edge (Chromium-based): unknown, no confirmed affected version
Fixed in
- Google Chrome 156.0.8078.47 per CVE text; secondary sources list 156.0.8078.47 or .48 for Windows and macOS, and 156.0.8078.47 for Linux (not confirmed on the vendor page)
- Later Stable builds exist; one secondary source lists 156.0.8078.79/.80 (Windows, macOS) and 156.0.8078.79 (Linux). Verify the current build on Google's advisory before setting a minimum version.
- Microsoft Edge: unknown
- Debian: fixed in DSA 6577-1 and DLA 4853-1
Workaround
- None known. The fix is a browser update.
Exploitation
- No exploitation in the wild known from the available sources.
- No public proof of concept found.
- No CISA KEV entry found.
- CISA SSVC assessment: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Google Chrome and all Chromium-based browsers (including Microsoft Edge) to the latest Stable build.
- Check the installed browser version on all endpoints and confirm that automatic updates work.
- Prioritise machines where browsers are not updated automatically or are managed inconsistently.
- Verify the score and status in the NVD and the fixed build on Google's advisory, as the sources disagree on the CVSS score (8.8 vs. 6.3).
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 517031871 issues.chromium.org
- VulDB CVE-2026-113332 vuldb.com
- Vulners CVE-2026-113332 vulners.com
- Ubuntu security CVE-2026-113332 ubuntu.com
- Strix CVE-2026-113332 www.strix.ai
- TechSpot Google Chrome download www.techspot.com
- Wikipedia: Google Chrome en.wikipedia.org
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, 11:53.
Original description (NVD)
Memory corruption in GPU 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: 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.