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-113159 Overview
CVE-2026-113159 is an improper access control vulnerability [CWE-284] in the DevTools component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to leak sensitive information through a crafted HTML page. Google rates the Chromium security severity as Medium. Exploitation requires user interaction, such as visiting a malicious website. Successful exploitation can disclose confidential data accessible through DevTools context without altering integrity or availability.
Critical Impact
A remote attacker can craft an HTML page that abuses DevTools access controls to leak sensitive information from the victim's browser session.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based builds incorporating the pre-patch DevTools component
- Downstream browsers that embed vulnerable Chromium releases
Discovery Timeline
- 2026-10-20 - CVE-2026-113159 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113159
Vulnerability Analysis
The vulnerability resides in Chrome DevTools, the built-in developer and debugging interface shipped with the browser. DevTools exposes privileged APIs and inspection surfaces that must be isolated from untrusted web content. In affected versions, access control checks around DevTools functionality are insufficient, allowing a crafted HTML page to reach information that should remain inaccessible to ordinary web origins. The disclosed data is limited to confidentiality impact, with no changes to integrity or availability of the browser or host system.
Root Cause
The root cause is improper access control [CWE-284] within the DevTools component. Boundary enforcement between untrusted renderer content and privileged DevTools surfaces fails under specific conditions crafted by an attacker. This allows a web page to influence or observe data flows normally scoped to the developer tooling context.
Attack Vector
Exploitation is network-based and requires user interaction. The victim must load an attacker-controlled HTML page in a vulnerable Chrome build. No authentication or elevated privileges are required on the target. Once the page is rendered, the crafted content triggers the access control gap in DevTools and extracts sensitive information observable to the attacker's script.
No verified public proof-of-concept code is available for this issue. Refer to the Chromium Issue Tracker entry for additional technical context as Google releases it.
Detection Methods for CVE-2026-113159
Indicators of Compromise
- Chrome browser process versions reporting below 156.0.8078.47 in endpoint inventory telemetry.
- Browser navigation events to untrusted domains immediately followed by outbound requests containing sensitive session data.
- Unexpected DevTools activity or protocol traffic (Chrome DevTools Protocol, port 9222) originating from user endpoints.
Detection Strategies
- Inventory installed Chrome versions across managed endpoints and flag any build earlier than 156.0.8078.47.
- Monitor web proxy and DNS logs for user navigation to newly registered or low-reputation domains serving HTML content.
- Correlate browser telemetry with data loss prevention events that identify sensitive data egress following page loads.
Monitoring Recommendations
- Enable browser management policies that report installed version and update channel to centralized logging.
- Ingest endpoint and proxy telemetry into a security data lake to retain navigation history for retrospective hunting.
- Alert on anomalous local listeners binding to Chrome DevTools debugging ports on user workstations.
How to Mitigate CVE-2026-113159
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all managed desktops.
- Validate that automatic updates are enabled and functioning across Windows, macOS, and Linux fleets.
- Restart Chrome after update to ensure the patched binary is loaded into memory.
Patch Information
Google addressed CVE-2026-113159 in the Stable channel desktop update to Chrome 156.0.8078.47. Deployment details are published in the Google Chrome Desktop Update release notes. Chromium-based browser vendors should incorporate the upstream fix referenced in the Chromium Issue Tracker Entry.
Workarounds
- Restrict user navigation to untrusted sites through enterprise web filtering until patching is complete.
- Deploy Chrome enterprise policies to limit extension installation and reduce exposure to malicious HTML payloads.
- Educate users to avoid opening unsolicited links, since exploitation requires loading a crafted page.
# Verify Chrome version on Linux and macOS endpoints
google-chrome --version
# Windows PowerShell check against installed Chrome build
(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

