Google Chrome: Improper input validation in Privacy component
Summary
An improper input validation flaw in the Privacy component of desktop Google Chrome before 156.0.8078.47 allows a remote attacker to potentially execute arbitrary code outside the browser sandbox. The attacker needs to lure a user to a crafted HTML page; no authentication is required. NVD rates the issue Critical (CVSS 3.1 9.6), while Google's Chromium security severity is Medium and VulDB lists a base score of 6.3.
Affected
- Google Chrome desktop builds prior to 156.0.8078.47
- Windows, macOS and Linux
Fixed in
- Google Chrome 156.0.8078.47 or later (minimum target; current stable build recommended)
- Third-party reporting cites 156.0.8078.73 or 156.0.8078.74 (Windows and Mac) and 156.0.8078.73 (Linux) as later stable builds; verify against the Chrome Releases blog
- Full fix list in the Chrome advisory not confirmed
Workaround
- Unknown. No vendor workaround identified; apply the update.
Exploitation
- Not listed in CISA KEV; EPSS unknown.
- No public proof of concept found.
- Exploitation in the wild: unknown (no evidence found).
- CISA SSVC: exploitation none, not automatable, total technical impact.
Our recommendation
- Verify that Chrome auto-update works and that all desktop browsers run the current stable build (at least 156.0.8078.47).
- Make sure users restart Chrome after the update, as the update applies only after a restart.
- Check managed and Chromium-based browsers (for example Microsoft Edge) separately and apply their updates.
- Monitor the Chromium issue tracker and 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
- NVD record via Vulners vulners.com
- VulDB entry vuldb.com
- Ubuntu security CVE page ubuntu.com
- Chrome security update guide (October 2026) sandbanksdigital.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 30 Oct 2026, 22:23.
Original description (NVD)
Improper input validation in Privacy in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code outside 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.