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-113097 Overview
CVE-2026-113097 is a use-after-free vulnerability in the FileSystem component of Google Chrome prior to version 156.0.8078.47. A remote attacker can exploit the flaw 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 High and tracked the issue in Chromium bug 526039697. The vulnerability maps to CWE-416: Use After Free and requires user interaction, typically visiting an attacker-controlled web page.
Critical Impact
Remote attackers can execute arbitrary code inside the Chrome renderer sandbox by convincing a user to load a crafted HTML page.
Affected Products
- Google Chrome versions prior to 156.0.8078.47 (Desktop Stable channel)
- Chromium-based browsers that embed the vulnerable FileSystem component
- All supported desktop platforms (Windows, macOS, Linux)
Discovery Timeline
- 2026-10-20 - CVE-2026-113097 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113097
Vulnerability Analysis
The flaw resides in Chrome's FileSystem implementation, which exposes JavaScript APIs for sandboxed file and directory access. A use-after-free occurs when the browser dereferences a FileSystem object after its backing memory has been released. The dangling pointer can be reclaimed by attacker-controlled data, giving the adversary control over object state or virtual function dispatch.
Because the FileSystem API is reachable from any origin running JavaScript, exploitation requires only that a user load a malicious page. Successful exploitation yields code execution within the renderer process, enabling further sandbox escape chains or data theft from the renderer context.
Root Cause
The underlying defect is classified as CWE-416: Use After Free. Chrome's FileSystem component releases an object while a reference remains reachable from JavaScript or internal browser code. Subsequent operations dereference the freed memory, producing an exploitable condition. Google has not published source-level details beyond the Chromium issue tracker reference.
Attack Vector
An attacker hosts a crafted HTML page that invokes specific FileSystem API sequences to trigger the free-then-reuse condition. The victim must load the page in a vulnerable Chrome build. No authentication is required. Delivery vectors include phishing links, malvertising, compromised sites, and watering-hole attacks. Exploitation produces arbitrary code execution confined to the renderer sandbox, which attackers typically chain with a sandbox escape to reach the host operating system.
Technical details are tracked in Chromium Issue #526039697 and the Google Chrome Stable Update advisory.
Detection Methods for CVE-2026-113097
Indicators of Compromise
- Chrome renderer processes crashing with heap corruption signatures after loading untrusted pages
- Unexpected child process creation spawned from chrome.exe or the renderer helper
- Outbound network connections from renderer processes to previously unseen domains following a page visit
- Browser telemetry showing active Chrome versions below 156.0.8078.47
Detection Strategies
- Inventory installed Chrome versions across managed endpoints and flag any build earlier than 156.0.8078.47
- Correlate renderer crash events (chrome.exe with FileSystem call stacks) with recent navigation history
- Monitor for anomalous process trees descending from browser processes, including shell or scripting hosts
- Alert on browser processes writing executables or scheduled tasks to disk
Monitoring Recommendations
- Collect Chrome crash reports and version telemetry centrally for triage
- Enable endpoint logging for process creation, image loads, and network connections tied to browser binaries
- Review web proxy logs for repeated visits to recently registered or low-reputation domains preceding renderer crashes
How to Mitigate CVE-2026-113097
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all desktop platforms
- Force-restart Chrome after deploying the patch to ensure the updated binary is loaded
- Audit third-party Chromium-based browsers and embedded WebView components for availability of equivalent fixes
- Prioritize patching for users with broad web browsing privileges and administrative accounts
Patch Information
Google released the fix in the Chrome Stable channel at version 156.0.8078.47. Deployment details are documented in the Google Chrome Stable Update release notes. Enterprises using Chrome Browser Enterprise should push the update through group policy or the preferred management console.
Workarounds
- No vendor-supplied workaround exists; apply the vendor patch as the primary remediation
- Restrict browsing to trusted sites via web filtering until all endpoints are updated
- Enforce Site Isolation and the strictest available sandbox policies through enterprise policy
- Disable or limit extensions that broaden the browser attack surface during the exposure window
# Verify installed Chrome version on Linux/macOS
google-chrome --version
# Windows: query the installed Chrome version via registry
reg query "HKLM\Software\Google\Chrome\BLBeacon" /v version
# Enterprise policy example: enforce auto-update minimum version
# Place in Chrome enterprise policy JSON
{
"BrowserSignin": 1,
"RelaunchNotification": 2,
"RelaunchNotificationPeriod": 86400000
}
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

