Google Chrome: Improper input validation in Loader allows sandbox code execution
Summary
Google Chrome versions before 156.0.8078.47 contain an improper input validation flaw in the Loader component. A remote attacker can potentially execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Google rates the issue Low in Chromium, and the NVD base score is 8.8 with user interaction required.
Affected
- Google Chrome prior to 156.0.8078.47
- The CVE record and NVD list the affected range as prior to 156.0.8078.47; third-party ranges differ and are unreliable.
Fixed in
- Chrome 156 stable, released 20 October 2026
- Linux: 156.0.8078.47
- Windows and macOS: 156.0.8078.47 or 156.0.8078.48 (sources differ; confirm in the vendor advisory)
Workaround
- No workaround needed once Chrome is updated to a fixed version.
- If updates are delayed: restrict browsing to trusted sites and use browser policies to limit risky content. This is general advice, not a vendor-documented mitigation.
Exploitation
- No known exploitation in the wild.
- No public proof of concept known.
- A third-party tracker lists the CVE as not in the CISA KEV catalogue; this is not verified against CISA.
- CISA SSVC assessment: exploitation none, not automatable, total technical impact.
Our recommendation
- Update Chrome to 156.0.8078.47 or later (Windows and macOS builds per the vendor advisory) on all managed devices through the normal Chrome rollout.
- Verify the installed version and make sure the browser was restarted after the update.
- Track Chromium-based browsers such as Edge separately, as they use the same Chromium fixes.
- Priority is low to medium on its own; handle it as part of the Chrome 156 update.
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 entry issues.chromium.org
- NVD record mirror (vulners.com) vulners.com
- VulDB entry (unreliable range, for reference) vuldb.com
- Chrome 156 security update overview (cybersecuritynews.com) cybersecuritynews.com
- Chrome 156 security update overview (windowsforum.com) windowsforum.com
- Google Chrome (Wikipedia) en.wikipedia.org
- Ubuntu CVE tracker entry ubuntu.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, 12:13.
Original description (NVD)
Improper input validation in Loader 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: Low)
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.