Google Chrome: Code execution in sandbox via improper input validation in Proxy
Summary
Google Chrome has an improper input validation flaw in its Proxy component. A remote attacker can potentially execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. NVD rates it CVSS 3.1 8.8 (High), and Chrome rates it High internally. User interaction is required, and a sandbox-confined compromise is more limited than full system takeover.
Affected
- Google Chrome prior to 156.0.8078.47
- Windows and macOS: require 156.0.8078.48 or later (per vendor-related sources)
- Edge (Chromium): one aggregator lists a range below 156.0.4314.42, not verified against Microsoft's advisory
Fixed in
- Linux: 156.0.8078.47 or later
- Windows and macOS: 156.0.8078.48 or later
- Later Stable and Extended Stable builds exist (reported as 156.0.8078.79/.80 for Windows and macOS, 156.0.8078.79 for Linux, per a third-party source); deploy the latest stable build
Workaround
- No vendor workaround found. Patching is the only confirmed mitigation.
- Ensure auto-update is active and verify the version (Menu > Help > About Google Chrome).
- Force updates on managed devices through policy.
Exploitation
- CISA SSVC assessment: Exploitation none, Automatable no, Technical Impact total.
- No evidence of exploitation in the wild found. CISA KEV status not verified at the CISA source.
- No public proof of concept found.
- EPSS: unknown.
Our recommendation
- Update Google Chrome on all endpoints to the latest stable build, at least 156.0.8078.48 on Windows and macOS.
- Enforce automatic updates through policy and check versions in managed fleets.
- Check Chromium-based browsers and Linux distribution packages for their own fixes.
- Prioritise workstations used for browsing and email; servers that do not browse have lower priority.
- Confirm NVD and CISA KEV status before closing the ticket.
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 568906040 issues.chromium.org
- HKCERT security bulletin: Google Chrome multiple vulnerabilities www.hkcert.org
- VulnERS NVD record CVE-2026-113040 vulners.com
- VulnERS MSCVE record CVE-2026-113040 vulners.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, 14:38.
Original description (NVD)
Improper input validation in Proxy 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.