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-110145 Overview
CVE-2026-110145 is a use-after-free vulnerability [CWE-416] in the Passwords component of Google Chrome versions prior to 155.0.8059.79. A remote attacker who has already compromised the renderer process can exploit the flaw to execute arbitrary code outside the Chromium sandbox. Exploitation requires user interaction with a crafted HTML page. Google tracks this issue in Chromium bug 562243925 and classifies the Chromium security severity as High.
Critical Impact
Successful exploitation enables sandbox escape and arbitrary code execution on the host, breaking a core Chromium security boundary.
Affected Products
- Google Chrome Desktop versions prior to 155.0.8059.79
- Chromium-based browsers incorporating the vulnerable Passwords component
- All desktop platforms supported by the Chrome Stable channel
Discovery Timeline
- 2026-10-13 - CVE-2026-110145 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-110145
Vulnerability Analysis
The flaw resides in the Passwords feature of Chrome's browser process. A use-after-free condition occurs when the browser accesses a heap object after it has already been released. Because Passwords runs in the privileged browser process, an attacker who already controls a renderer can send crafted inter-process communication (IPC) messages to trigger the dangling pointer. This chains with a compromised renderer to escape the sandbox.
Sandbox escape vulnerabilities in Chromium are considered high impact because they break the primary isolation boundary between untrusted web content and the operating system. The attacker gains the privileges of the browser process, which can read user data, write to disk, and launch child processes.
Root Cause
The root cause is improper lifetime management of a heap-allocated object within the Passwords subsystem. The affected code path releases the object while another reference still points to it, allowing a subsequent operation to dereference freed memory. This matches the [CWE-416] use-after-free pattern typical of complex, asynchronous C++ components in Chromium.
Attack Vector
Exploitation is a two-stage process. First, the attacker compromises the renderer process, typically through a prior memory-corruption bug triggered by a crafted HTML page. Second, the attacker leverages IPC calls to the Passwords component to trigger the use-after-free in the browser process. User interaction with the malicious page is required.
No verified public exploit code is available at this time. Technical details are tracked in the Chromium Issue Tracker #562243925 and summarized in the Google Chrome Desktop Update.
Detection Methods for CVE-2026-110145
Indicators of Compromise
- Chrome renderer or browser process crashes referencing the Passwords component in crash dumps
- Unexpected child processes spawned by chrome.exe following interaction with untrusted web content
- Outbound network connections from the browser process to attacker-controlled infrastructure immediately after a page load
Detection Strategies
- Inventory installed Chrome builds and flag any version earlier than 155.0.8059.79 as vulnerable
- Monitor endpoint telemetry for Chrome processes performing anomalous file writes, registry edits, or process launches
- Correlate browser crash events with subsequent process creation to identify potential sandbox-escape chains
Monitoring Recommendations
- Collect and retain Chromium crash reports to support post-incident analysis of memory-corruption bugs
- Enable browser-process creation and network telemetry in endpoint detection and response (EDR) tooling
- Alert on execution of binaries from Chrome user-data or temporary directories
How to Mitigate CVE-2026-110145
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.79 or later on all desktop endpoints
- Restart Chrome after the update to ensure the patched binary is loaded
- Audit managed browser deployments and enforce automatic updates through group policy or MDM
Patch Information
Google addressed the issue in the Chrome Stable channel release documented in the Chrome Releases blog post. Chromium-based browser vendors should incorporate the upstream fix referenced in Chromium Issue #562243925 and ship updated builds to their users.
Workarounds
- No vendor-supplied workaround exists; patching is the only reliable remediation
- Restrict browsing to trusted sites and enforce web-content filtering until updates are deployed
- Disable or restrict password-manager features where organizational policy permits, acknowledging this does not fully eliminate the attack surface
# Verify installed Chrome version on Windows
reg query "HKLM\Software\Google\Chrome\BLBeacon" /v version
# Verify installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Verify installed Chrome version on Linux
google-chrome --version
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

