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-106372 Overview
CVE-2026-106372 is an incorrect authorization vulnerability in the user interface component of Google Chrome prior to version 155.0.8059.39. A remote attacker can exploit the flaw by serving a crafted HTML page, potentially executing arbitrary code outside the browser sandbox. The weakness is classified under CWE-863: Incorrect Authorization. Successful exploitation requires user interaction, such as visiting a malicious website. Chromium rates the underlying security severity as Medium, while the NVD score reflects the sandbox escape impact.
Critical Impact
A sandbox escape in Chrome allows attacker-controlled code to run outside the renderer boundary, breaking the primary isolation layer that protects the host operating system from untrusted web content.
Affected Products
- Google Chrome versions prior to 155.0.8059.39 (Desktop Stable channel)
- Chromium-based browsers inheriting the vulnerable UI authorization logic
- All desktop platforms shipping the affected Stable channel build
Discovery Timeline
- 2026-10-06 - CVE-2026-106372 published to NVD
- 2026-10-07 - Last updated in NVD database
- 2026-10 - Google releases fixed Chrome Stable channel build 155.0.8059.39 (Chrome Releases blog)
Technical Details for CVE-2026-106372
Vulnerability Analysis
The flaw resides in Chrome's UI layer, where an authorization check does not correctly validate the privilege or origin context before permitting an action. An attacker who lures a user to a crafted HTML page can trigger the mis-authorized UI path. This path provides a bridge from the sandboxed renderer to higher-privileged browser functionality. The outcome, as described in Google's advisory, is potential arbitrary code execution outside the Chrome sandbox. Sandbox escapes are weighted heavily because they defeat the renderer isolation model that Chrome relies on to contain untrusted web content. Full technical details remain restricted in the Chromium issue tracker #557288890 pending broad patch adoption.
Root Cause
The root cause is improper authorization enforcement in a UI code path (CWE-863). The affected logic grants an action or capability without confirming the caller holds the required permissions or originates from a trusted surface. This mismatch between intended policy and enforced checks allows a web-origin page to invoke functionality that should be gated to the browser process.
Attack Vector
Exploitation requires a victim to load attacker-controlled HTML in a vulnerable Chrome build. No credentials are required, and the attack is delivered over the network. The crafted page interacts with the vulnerable UI surface to induce the unauthorized action and chain to code execution outside the sandbox. Because the sandbox boundary is crossed, scope changes from the renderer to the broader host context.
No public proof-of-concept or exploit code has been released. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog, and no in-the-wild exploitation has been reported at the time of publication.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-106372
Indicators of Compromise
- Chrome chrome.exe or chrome processes spawning unexpected child processes such as cmd.exe, powershell.exe, or shell interpreters following a browsing session
- Writes to persistence locations (Run keys, Scheduled Tasks, LaunchAgents, cron) from Chrome process trees
- Outbound connections from non-renderer Chrome child processes to unfamiliar domains or IP addresses shortly after a page load
Detection Strategies
- Inventory installed Chrome versions across endpoints and alert on any build earlier than 155.0.8059.39
- Hunt for anomalous process lineage where a Chrome browser process is the parent of script interpreters or native binaries not associated with normal browser operation
- Correlate browser telemetry with endpoint EDR Storyline data to identify sandbox-escape patterns following HTML page loads
Monitoring Recommendations
- Enable browser version reporting through enterprise management (Chrome Browser Cloud Management or Group Policy) and dashboard non-compliant hosts
- Forward Chrome crash reports and renderer-exit telemetry to the SIEM for correlation with suspicious URL categories
- Monitor for new executables written under user profile directories immediately after Chrome activity
How to Mitigate CVE-2026-106372
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.39 or later on all Windows, macOS, and Linux endpoints
- Force-restart Chrome processes after deployment, as patched binaries only take effect on relaunch
- Audit Chromium-based browsers and embedded Chromium frameworks in internal applications for the same vulnerable code
- Prioritize patching for high-risk user populations such as executives, developers, and administrators
Patch Information
Google addressed the issue in the Stable channel desktop update tracked in the Chrome Releases announcement. The fixed version is 155.0.8059.39. Enterprise administrators should validate the rollout through the Chrome admin console and confirm that managed devices report the patched build.
Workarounds
- No vendor-supplied workaround exists; updating to the patched Chrome build is the only supported remediation
- Restrict browsing to trusted sites through enterprise URL filtering until patch deployment completes
- Enforce the principle of least privilege on endpoints so that any sandbox escape runs with limited user rights rather than administrative privileges
- Disable or restrict unnecessary Chrome extensions that broaden the UI attack surface
# Verify installed Chrome version on Linux/macOS
google-chrome --version
# Expected output: Google Chrome 155.0.8059.39 or later
# Windows (PowerShell) - query installed Chrome version
(Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
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

