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-113189 Overview
CVE-2026-113189 is a use-after-free vulnerability in the Core component of Google Chrome versions prior to 156.0.8078.47. A remote attacker can exploit the flaw by serving a crafted HTML page, triggering execution of arbitrary code outside the browser sandbox. The vulnerability is classified under CWE-416: Use After Free. Google rates the Chromium security severity as Medium, while the National Vulnerability Database assigns a Critical rating due to the sandbox escape and remote attack vector. Successful exploitation requires minimal user interaction, such as visiting an attacker-controlled web page.
Critical Impact
Remote attackers can execute arbitrary code outside the Chrome sandbox by luring users to a malicious HTML page, bypassing a key browser security boundary.
Affected Products
- Google Chrome versions prior to 156.0.8078.47 (Desktop Stable channel)
- Chromium-based browsers that inherit the vulnerable Core component
- Enterprise deployments of Chrome on Windows, macOS, and Linux
Discovery Timeline
- 2026-10-20 - CVE-2026-113189 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113189
Vulnerability Analysis
The flaw resides in the Core component of Chrome, which handles fundamental browser engine operations. A use-after-free condition occurs when the browser references a memory region after it has already been freed. An attacker who controls the contents and timing of allocations can place attacker-chosen data into the reclaimed region. Dereferencing this stale pointer leads to memory corruption that an attacker can shape into arbitrary code execution.
What distinguishes this issue from typical renderer-only bugs is that exploitation leads to code execution outside the Chrome sandbox. The sandbox normally confines renderer processes to a restricted environment with minimal operating system privileges. Bypassing it gives the attacker the same privileges as the Chrome process, enabling file access, process creation, and persistence on the host.
Root Cause
The root cause is improper lifetime management of an object within Chrome Core. Code paths retain a reference to an object that has been destroyed, violating the memory ownership contract. The Chromium issue tracker entry (Issue #514016335) contains the restricted technical details, which Google withholds until a majority of users have updated.
Attack Vector
Exploitation is network-based and requires user interaction. The attacker hosts a crafted HTML page containing JavaScript, Document Object Model (DOM) manipulation, or other web content designed to trigger the vulnerable code path. When a victim visits the page, the renderer executes the exploit sequence, frees the target object, reallocates the memory with attacker-controlled content, and reuses the stale reference. The resulting primitive is chained with additional techniques to escape the sandbox and run native code.
No public proof-of-concept is available at this time, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2026-113189
Indicators of Compromise
- Chrome processes spawning unexpected child processes such as cmd.exe, powershell.exe, or shell interpreters immediately after browsing activity.
- Unexpected file writes under user profile directories originating from the Chrome process.
- Outbound network connections from Chrome to newly registered or low-reputation domains hosting HTML content.
- Chrome renderer or browser process crashes with access violation signatures correlated with specific URLs.
Detection Strategies
- Inventory Chrome installations across the environment and flag any version below 156.0.8078.47.
- Monitor process lineage for Chrome parent processes launching binaries outside the standard Chrome execution tree.
- Correlate browser crash telemetry with proxy and DNS logs to identify suspicious URLs preceding the crash.
- Apply behavioral analytics to detect sandbox escape patterns, including unexpected inter-process communication or token manipulation.
Monitoring Recommendations
- Ingest Chrome version telemetry from endpoint management tools into the security information and event management (SIEM) platform.
- Alert on Chrome processes performing privileged operations such as registry modification, scheduled task creation, or credential store access.
- Track browser extension and update activity to detect tampering that might disable auto-update.
How to Mitigate CVE-2026-113189
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all desktop endpoints.
- Restart Chrome after the update to ensure the patched binaries are loaded into memory.
- Verify Chrome auto-update is enabled and functional through enterprise management policies.
- Prioritize patching for high-risk users such as administrators, developers, and executives.
Patch Information
Google released the fix in the Stable channel update documented in the Google Chrome Stable Update advisory. Enterprises using managed deployments should distribute the updated MSI, PKG, or DEB packages through their standard software distribution channels. Chromium-based downstream browsers should apply vendor updates incorporating the upstream fix.
Workarounds
- Restrict browsing to trusted sites using web proxy and URL filtering controls until patching completes.
- Enforce Site Isolation and strict sandbox policies via Chrome enterprise policy to raise exploitation cost.
- Disable or restrict JavaScript on untrusted origins where feasible through enterprise content settings.
- Deploy browser isolation technology for users who routinely access untrusted web content.
# Verify Chrome version on Linux endpoints
google-chrome --version
# Example enterprise policy to force auto-update (Windows registry)
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v UpdateDefault /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v AutoUpdateCheckPeriodMinutes /t REG_DWORD /d 60 /f
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

