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-113095 Overview
CVE-2026-113095 is an out-of-bounds read vulnerability in the Focus component of Google Chrome prior to version 156.0.8078.47. A remote attacker can exploit this flaw by serving a crafted HTML page to a victim. Successful exploitation allows arbitrary code execution inside the Chrome sandbox. The Chromium project classifies the security severity as High, and the vulnerability is tracked under CWE-125 (Out-of-bounds Read).
Exploitation requires user interaction, specifically visiting an attacker-controlled web page. No public proof-of-concept, in-the-wild exploitation, or CISA KEV listing has been reported at the time of publication.
Critical Impact
Remote attackers can execute arbitrary code within the Chrome renderer sandbox by convincing a user to load a malicious HTML page.
Affected Products
- Google Chrome for Desktop versions prior to 156.0.8078.47
- Chromium-based browsers that inherit the vulnerable Focus component
- All platforms shipped from the Chrome Stable channel before the October 2026 update
Discovery Timeline
- 2026-10-20 - CVE-2026-113095 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113095
Vulnerability Analysis
The vulnerability is an out-of-bounds read [CWE-125] in Chrome's Focus handling logic. The Focus subsystem manages which DOM element currently receives keyboard input and related UI events. When processing a crafted HTML page, the component reads memory outside the bounds of an intended buffer or object.
Attackers can combine the information leaked by the out-of-bounds read with memory-corruption primitives to bypass mitigations such as Address Space Layout Randomization. According to the NVD description, successful exploitation results in arbitrary code execution inside the Chrome sandbox, giving the attacker control of the renderer process. A sandbox escape would be required to achieve full compromise of the host.
Root Cause
The root cause is missing or incorrect boundary validation inside the Focus component when parsing or responding to attacker-controlled HTML and DOM state. The affected code path dereferences a pointer or index without verifying it falls within the allocated range of the target object. No vendor technical write-up has been published beyond Chromium Issue #570167919, which remains access-restricted during the standard disclosure embargo.
Attack Vector
The attack vector is network-based through standard web browsing. An attacker hosts a malicious HTML page or compromises an existing site to deliver crafted markup, scripts, or focus-manipulating sequences. When a victim loads the page in a vulnerable Chrome build, the Focus component triggers the out-of-bounds read. Secondary vectors include malicious advertisements, embedded iframes on otherwise trusted sites, and phishing links delivered through email or messaging platforms.
No verified exploit code is publicly available. Refer to the Google Chrome Stable Update advisory for vendor guidance.
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-113095
Indicators of Compromise
- Chrome renderer processes crashing with access violation or segmentation faults shortly after visiting an unfamiliar URL
- Browser telemetry showing child renderer processes spawning unexpected child processes or writing to disk outside standard cache locations
- Outbound connections from chrome.exe to recently registered or low-reputation domains following a page load
Detection Strategies
- Inventory installed Chrome versions across the fleet and alert on any build earlier than 156.0.8078.47
- Correlate web proxy logs with endpoint telemetry to identify users who visited suspicious pages immediately before a Chrome crash event
- Deploy YARA or behavioral rules that detect post-exploitation activity originating from browser child processes, such as script interpreter or LOLBAS execution
Monitoring Recommendations
- Forward Chrome crash dumps and Windows Error Reporting telemetry to a central SIEM for triage
- Monitor DNS and HTTP egress for connections to domains flagged in Chrome exploit kit threat intelligence feeds
- Track browser version compliance as a continuous control rather than a point-in-time audit
How to Mitigate CVE-2026-113095
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all desktop platforms
- Restart Chrome after the update installs so the patched binary is loaded into memory
- Verify managed browser policies to confirm automatic updates are not disabled on corporate endpoints
Patch Information
Google released the fix in the Chrome Stable channel update documented in the Google Chrome Stable Update advisory. Users should upgrade to Chrome 156.0.8078.47 or later. Chromium-based browser vendors typically ship the same fix within days of upstream disclosure. Confirm patch status for Microsoft Edge, Brave, Opera, and other derivatives through their respective release notes.
Workarounds
- Restrict high-risk browsing to isolated or ephemeral virtual machines until all endpoints are patched
- Enforce site isolation and strict Enhanced Safe Browsing policies through Chrome enterprise configuration
- Block or sandbox untrusted JavaScript execution through enterprise web filtering until patch deployment is confirmed
# Verify installed Chrome version on Windows via PowerShell
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
# 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

