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-113168 Overview
CVE-2026-113168 is a use-after-free vulnerability [CWE-416] in the Permissions component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can exploit the issue by serving a crafted HTML page to a target user. Successful exploitation allows arbitrary code execution inside the Chrome sandbox. Google classified the Chromium security severity as Low, while the National Vulnerability Database (NVD) rates it HIGH based on impact and network reachability. The vulnerability requires user interaction, such as visiting an attacker-controlled page.
Critical Impact
Remote attackers can execute arbitrary code within the Chrome sandbox by luring users to a crafted web page, providing an initial foothold for further exploitation chains.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based builds incorporating the vulnerable Permissions component
- All supported desktop platforms (Windows, macOS, Linux) running affected Chrome releases
Discovery Timeline
- 2026-10-20 - CVE-2026-113168 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113168
Vulnerability Analysis
The vulnerability resides in the Permissions subsystem of Chrome, which brokers user consent for sensitive browser APIs such as geolocation, notifications, camera, and microphone access. A use-after-free condition occurs when the Permissions component references a heap object that has already been freed. An attacker who controls the allocation and deallocation sequence can reclaim the freed memory with attacker-chosen data. Dereferencing the stale pointer then redirects control flow or corrupts object state. The resulting primitive enables arbitrary code execution within the Chrome sandbox process.
Root Cause
The root cause is improper lifetime management of a Permissions object [CWE-416]. The Permissions code retains a raw pointer or reference to an object whose owner releases it during asynchronous permission handling. Subsequent operations on the dangling reference trigger the memory safety violation.
Attack Vector
Exploitation requires network delivery and user interaction. An attacker hosts a crafted HTML page that invokes Permissions APIs in a sequence designed to trigger the free and subsequent reuse. When a user visits the page, the renderer executes attacker-supplied JavaScript that drives the vulnerable code path. Code execution is confined to the Chrome sandbox, but attackers typically chain such flaws with a sandbox escape for full system compromise.
No verified public proof-of-concept is available. Refer to the Chromium Issue Tracker Entry once access restrictions are lifted and to the Chrome Desktop Update Release for vendor details.
Detection Methods for CVE-2026-113168
Indicators of Compromise
- Chrome renderer process crashes with heap-use-after-free signatures referencing Permissions code paths
- Outbound connections from browser processes to newly registered or low-reputation domains following user navigation
- Unexpected child processes spawned by chrome.exe or the renderer helper on macOS and Linux
Detection Strategies
- Inventory installed Chrome builds across the fleet and flag versions prior to 156.0.8078.47
- Monitor browser process telemetry for anomalous memory access violations and renderer crashes correlated with web navigation
- Correlate web proxy logs with endpoint telemetry to identify users who visited suspicious pages immediately before browser instability
Monitoring Recommendations
- Enable crash reporting and forward Chrome crash dumps to a central analysis pipeline
- Alert on process injection, token manipulation, or unexpected shell execution originating from Chrome processes
- Track permission-prompt abuse patterns in enterprise browser management consoles
How to Mitigate CVE-2026-113168
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all desktop endpoints
- Validate that managed Chrome deployments received the stable channel update and restart browsers to apply the fix
- Audit third-party Chromium-based browsers and embedded webviews for pending upstream patches
Patch Information
Google fixed the vulnerability in Chrome stable channel release 156.0.8078.47. Deployment details are documented in the Chrome Desktop Update Release. Enterprise administrators should push the update through Google Update, Chrome Browser Cloud Management, or their standard patch management workflow.
Workarounds
- Restrict access to untrusted websites through enterprise web filtering until patching is complete
- Enforce site isolation and Chrome's strict permissions policies via group policy to reduce attack surface
- Disable or constrain sensitive permission APIs for untrusted origins where business requirements allow
# Verify installed Chrome version on Linux
google-chrome --version
# Windows: query installed version via registry
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv
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

