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-113142 Overview
CVE-2026-113142 is a memory corruption vulnerability in the Extensions component of Google Chrome prior to version 156.0.8078.47. A remote attacker can craft a malicious HTML page that triggers the flaw, enabling the attacker to read memory inside the Chrome sandbox. Exploitation requires user interaction, typically visiting an attacker-controlled page. Google tracks the issue under Chromium security severity Medium and classifies it as a memory corruption weakness ([CWE-119]).
Critical Impact
Successful exploitation discloses sandboxed renderer memory to a remote attacker, potentially leaking sensitive browser process data such as tokens, URLs, or cross-origin content.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based builds integrating the vulnerable Extensions component
- Downstream browsers that embed Chromium Extensions code prior to the fixed release
Discovery Timeline
- 2026-10-20 - CVE-2026-113142 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113142
Vulnerability Analysis
The vulnerability resides in the Extensions subsystem of Chrome, which handles communication, lifecycle, and resource management for installed browser extensions. Memory corruption in this component permits a remote attacker to read memory inside the renderer sandbox. The flaw is classified under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer), indicating that extension-related code performs memory operations without properly enforcing size or bounds constraints. Because the leak occurs inside the sandbox rather than the broader operating system, impact is bounded to information disclosure rather than full code execution. Exploited data may still include sensitive content handled by the renderer, such as session tokens, DOM content, or cross-origin material processed during the attack.
Root Cause
The root cause is improper memory boundary handling within the Chrome Extensions code path. Attacker-controlled HTML triggers an operation that reads beyond an intended buffer or references memory in an unsafe way, exposing adjacent process memory. Full technical details are tracked in Chromium Issue 498733953.
Attack Vector
Exploitation occurs over the network and requires the victim to load a crafted HTML page in a vulnerable Chrome build. No authentication is required, but user interaction is necessary. An attacker can deliver the payload through a malicious site, a compromised third-party advertisement, or an embedded iframe on an otherwise legitimate page. Once the page is rendered, the attacker-controlled script interacts with the Extensions component to trigger the memory read.
No public proof-of-concept exploit is listed in Exploit-DB, and the vulnerability is not present on the CISA Known Exploited Vulnerabilities list. For technical artifacts, refer to Chromium Issue Attachment #75108978.
Detection Methods for CVE-2026-113142
Indicators of Compromise
- Chrome renderer processes crashing or restarting shortly after visiting unfamiliar HTML pages that interact with extension APIs.
- Outbound requests from browser hosts to recently registered or low-reputation domains serving HTML that aggressively probes extension messaging.
- Browser telemetry showing Chrome versions earlier than 156.0.8078.47 still active in the environment after the patch window.
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 domains hosting pages that trigger abnormal renderer behavior or crash reports.
- Correlate Chrome crash dumps referencing the Extensions component with the user's recent browsing history to identify exploitation attempts.
Monitoring Recommendations
- Collect browser process telemetry (process creation, crashes, child processes) into a central data lake for cross-host correlation.
- Alert on repeated renderer crashes affecting the same user within short time windows, which may indicate exploitation attempts.
- Track extension installation events and extension-origin network traffic to detect secondary tooling that could pair with this information disclosure.
How to Mitigate CVE-2026-113142
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all managed desktops.
- Verify auto-update is enabled and functional, then force a browser restart to apply the patched binaries.
- Audit third-party Chromium-based browsers for upstream merges that include the fix before marking them patched.
Patch Information
Google addressed the vulnerability in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. Administrators should ensure endpoints receive 156.0.8078.47 or newer. Enterprise deployments using Chrome Browser Cloud Management or group policy should confirm the update rollout schedule and relaunch policies are enforced.
Workarounds
- Restrict installation of untrusted extensions via enterprise policy to reduce the attack surface in the Extensions component.
- Enforce strict web filtering and block categories commonly abused for drive-by exploitation until patching completes.
- Configure Chrome enterprise policy to require browser relaunch within a short grace period after updates become available.
# Configuration example: enforce minimum Chrome version via enterprise policy (Linux example)
# /etc/opt/chrome/policies/managed/chrome_update_policy.json
{
"RelaunchNotification": 2,
"RelaunchNotificationPeriod": 86400000,
"ExtensionInstallBlocklist": ["*"],
"ExtensionInstallAllowlist": ["<approved-extension-id>"]
}
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

