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-113014 Overview
CVE-2026-113014 is a use-after-free vulnerability in the PerformanceAPIs component of Google Chrome. The flaw affects all Chrome Desktop versions prior to 156.0.8078.47. A remote attacker can trigger the condition by serving a crafted HTML page to a victim. Successful exploitation allows arbitrary code execution outside the Chrome sandbox, which breaks a key security boundary of the browser. Google categorized the Chromium severity as Medium, but the published CVSS metrics place the issue in the critical range because of the scope change and sandbox escape potential.
Critical Impact
Remote attackers can execute arbitrary code outside the Chrome sandbox when a user visits a malicious web page, enabling full browser compromise and potential host-level code execution.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based browsers that embed the vulnerable PerformanceAPIs component
- Downstream distributions pending vendor rebuilds against the patched Chromium branch
Discovery Timeline
- 2026-10-20 - CVE-2026-113014 published to the National Vulnerability Database
- 2026-10-21 - NVD record last modified
Technical Details for CVE-2026-113014
Vulnerability Analysis
The vulnerability is a use-after-free [CWE-416] in the PerformanceAPIs implementation inside Chromium's renderer. Use-after-free conditions arise when code dereferences a pointer to memory that has already been released back to the allocator. In browser engines, these conditions commonly stem from object lifetimes that outlive their owning context during asynchronous operations or garbage collection cycles.
An attacker who controls page content can orchestrate the sequence of API calls needed to free an underlying C++ object while a JavaScript handle to it remains live. When the handle is next used, the freed memory can be reclaimed by attacker-controlled data, enabling control of a vtable or function pointer. Chromium's threat model treats this as particularly severe because the advisory indicates exploitation can escape the renderer sandbox, giving the attacker code execution in a less-restricted process context.
Root Cause
The root cause is improper lifetime management of an object referenced by the PerformanceAPIs surface. The specific object relationship and the exact trigger have not been publicly disclosed; the Chromium Issue Tracker entry 502251640 remains restricted pending broad patch adoption.
Attack Vector
Exploitation requires a victim to load attacker-controlled HTML in a vulnerable Chrome build. The attack vector is network-based with user interaction limited to visiting a web page. No authentication is required. The scope change in the CVSS vector reflects the sandbox escape, where code executed in the compromised renderer can affect resources beyond its original security authority.
No public proof-of-concept or exploit code is available at the time of writing. Technical specifics are described in the Chromium Issue Tracker Entry.
Detection Methods for CVE-2026-113014
Indicators of Compromise
- Chrome renderer processes spawning unexpected child processes such as command shells, scripting hosts, or rundll32
- Unusual network connections initiated by chrome.exe to attacker infrastructure immediately after a browsing session
- Crash dumps referencing PerformanceAPIs or heap corruption in freed objects within the Blink renderer
Detection Strategies
- Monitor for anomalous process trees originating from Chrome renderer processes, which should not normally fork native tooling
- Inspect browser telemetry and crash reports for repeated faults in the PerformanceAPIs code path
- Use web proxy or DNS logs to identify users visiting newly registered or low-reputation domains serving heavy JavaScript payloads targeting performance timing APIs
Monitoring Recommendations
- Alert on Chrome versions below 156.0.8078.47 reported by endpoint inventory tools
- Track execution of binaries written to user-writable paths shortly after browser activity
- Correlate EDR process and network telemetry to detect post-exploitation activity following a sandbox escape
How to Mitigate CVE-2026-113014
Immediate Actions Required
- Update Google Chrome Desktop to version 156.0.8078.47 or later across all managed endpoints
- Force-restart Chrome after the update so the new binaries load; pending updates do not take effect in long-running sessions
- Audit Chromium-based browsers and embedded WebViews in your estate and apply vendor updates as they ship
Patch Information
Google released the fix in the Chrome Stable channel. See the Google Chrome Desktop Update advisory for the full release notes and version mapping per platform.
Workarounds
- No vendor-supplied workaround exists; patching is the only supported remediation
- Restrict browsing to trusted sites via enterprise web filtering until all endpoints are updated
- Enforce site isolation and consider disabling JavaScript on untrusted origins through enterprise policy for high-risk users
# Verify installed Chrome version on Windows endpoints
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv
# Verify installed Chrome version on macOS endpoints
defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString
# Verify installed Chrome version on Linux endpoints
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

