Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106390 Overview
CVE-2026-106390 is an information disclosure vulnerability in the SanitizerAPI component of Google Chrome prior to version 155.0.8059.39. A remote attacker can leak sensitive information by serving a crafted HTML page to a victim. The flaw is tracked under CWE-684: Incorrect Provision of Specified Functionality, meaning the API returns results inconsistent with its documented security guarantees. Chromium classifies the security severity as Low, and successful exploitation requires user interaction such as visiting an attacker-controlled page.
Critical Impact
A remote attacker can leak sensitive information from the browser context when a user visits a crafted HTML page.
Affected Products
- Google Chrome versions prior to 155.0.8059.39
- Chromium-based browsers incorporating the vulnerable SanitizerAPI implementation
- Desktop Chrome Stable channel builds released before the October 2026 update
Discovery Timeline
- 2026-10-06 - CVE-2026-106390 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-106390
Vulnerability Analysis
The vulnerability resides in Chrome's SanitizerAPI, a browser interface designed to sanitize untrusted HTML before insertion into the DOM. The API fails to correctly enforce its specified behavior, allowing a crafted HTML page to extract information that should remain isolated. The exploitation requires the victim to load attacker-controlled content, consistent with the user interaction requirement in the CVSS vector. The confidentiality impact is limited, with no effect on integrity or availability. No public proof-of-concept, exploit code, or evidence of exploitation in the wild has been reported, and the CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.
Root Cause
The root cause maps to CWE-684: the SanitizerAPI provides functionality that does not match its documented security contract. Specifically, the sanitizer permits content or behavior that enables an attacker to observe data the API should have blocked or neutralized. Chromium issue tracker entry #556213916 contains the restricted technical details.
Attack Vector
An attacker hosts a crafted HTML page and lures a victim running a vulnerable Chrome build to visit it. The page invokes the SanitizerAPI in a way that triggers the incorrect behavior, exposing sensitive information to the attacker's JavaScript context. No authentication or elevated privileges are required. See the Google Chrome Stable Update advisory for vendor-level context on the affected build.
// No verified exploit code is publicly available for CVE-2026-106390.
// Technical details are restricted in Chromium issue #556213916.
Detection Methods for CVE-2026-106390
Indicators of Compromise
- No file-based or network IOCs have been published for CVE-2026-106390.
- Suspicious outbound requests from browser processes to unknown domains immediately after loading unfamiliar HTML content.
- Browser telemetry showing use of Sanitizer or setHTML APIs on untrusted pages followed by exfiltration-shaped traffic.
Detection Strategies
- Inventory Chrome installations and flag any instance running a version earlier than 155.0.8059.39.
- Monitor web proxy logs for user visits to low-reputation domains that serve HTML interacting with the SanitizerAPI.
- Correlate browser process network activity with endpoint telemetry to identify data-shaped responses leaving the browser sandbox.
Monitoring Recommendations
- Enable browser version reporting through enterprise management (Chrome Browser Cloud Management) to track patch compliance.
- Alert on Chrome child processes making unexpected outbound connections shortly after page load events.
- Review DLP logs for small, repeated data transfers originating from browser sessions on unpatched hosts.
How to Mitigate CVE-2026-106390
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.39 or later on all Windows, macOS, and Linux endpoints.
- Restart Chrome after the update to ensure the patched binary is loaded into memory.
- Verify Chromium-based third-party browsers have pulled in the equivalent upstream fix.
Patch Information
Google addressed the issue in Chrome Stable 155.0.8059.39. Patch details are documented in the Google Chrome Stable Channel Update. Administrators should push the update through their standard browser management tooling and confirm end-user restart.
Workarounds
- Restrict user browsing to trusted domains using web filtering or secure web gateway policies until patches are deployed.
- Disable or limit experimental web platform features in managed Chrome policies where feasible.
- Educate users to avoid clicking unsolicited links, since exploitation requires loading a crafted HTML page.
# Verify installed Chrome version on Linux endpoints
google-chrome --version
# Enterprise policy: force auto-update to the latest Stable channel
# /etc/opt/chrome/policies/managed/update_policy.json
# {
# "TargetChannel": "stable",
# "UpdateDefault": 1
# }
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

