Skip to main content
Vulnerability Database/CVE-2026-113019

CVE-2026-113019: Google Chrome Use After Free Vulnerability

CVE-2026-113019 is a use after free vulnerability in Google Chrome Turbolev component that enables remote attackers to execute arbitrary code within the sandbox. This article covers technical details, affected versions, and mitigation.

Published:

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-113019 Overview

CVE-2026-113019 is a use-after-free vulnerability [CWE-416] in the Turbolev component of Google Chrome versions prior to 156.0.8078.47. A remote attacker can execute arbitrary code inside the Chrome sandbox by convincing a user to visit a crafted HTML page. Google rated the Chromium security severity as High. Exploitation requires user interaction, specifically rendering the attacker-controlled page in a vulnerable Chrome build. Successful exploitation yields code execution confined to the renderer sandbox, which attackers typically chain with a sandbox escape to achieve full compromise.

Critical Impact

Remote attackers can execute arbitrary code within the Chrome renderer sandbox by serving a malicious HTML page to users running Chrome versions earlier than 156.0.8078.47.

Affected Products

  • Google Chrome versions prior to 156.0.8078.47 on desktop platforms
  • Chromium-based browsers that embed the vulnerable Turbolev component
  • Downstream distributions pending vendor rebuilds of the Chromium engine

Discovery Timeline

  • 2026-10-20 - CVE-2026-113019 published to the National Vulnerability Database
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-113019

Vulnerability Analysis

The flaw resides in Turbolev, a component within the Chromium rendering stack. A use-after-free condition occurs when the component continues to reference heap memory after it has been released. An attacker crafts an HTML page that triggers the specific sequence of allocations, deallocations, and reuse required to reach the dangling reference. Once the freed memory is reclaimed with attacker-controlled data, control-flow hijacking becomes possible inside the renderer process.

Exploitation produces arbitrary code execution confined to the sandbox. Attackers commonly pair renderer bugs with a separate sandbox escape to reach the host operating system. The vulnerability requires user interaction, limiting drive-by exposure to users who visit attacker-controlled or compromised sites.

Root Cause

The root cause is improper object lifetime management inside Turbolev. The component dereferences a pointer to an object that has already been freed, violating heap invariants. Technical specifics are tracked in the restricted Chromium Issue Tracker Entry, which Google typically keeps embargoed until a majority of users patch.

Attack Vector

The attack vector is network-based with required user interaction. An attacker hosts a crafted HTML page or injects malicious markup into a site the user visits. When the browser parses the page, Turbolev enters the vulnerable state and the use-after-free is triggered. No authentication is required, and the attack surface includes any site rendered by vulnerable Chrome builds, including advertisements and third-party iframes.

No public proof-of-concept or exploit code is available at the time of publication. Verified technical details are described in prose only; see the Google Chrome Stable Update advisory for release notes.

Detection Methods for CVE-2026-113019

Indicators of Compromise

  • Chrome renderer process crashes with heap corruption signatures correlated to recent browsing activity
  • Unexpected child process creation from chrome.exe following navigation to an untrusted URL
  • Outbound connections from renderer processes to previously unseen command-and-control infrastructure
  • Browser telemetry showing Chrome versions below 156.0.8078.47 on managed endpoints

Detection Strategies

  • Inventory installed Chrome versions across the fleet and flag any build earlier than 156.0.8078.47
  • Monitor for anomalous process trees descending from Chrome renderer processes
  • Correlate web proxy logs with endpoint telemetry to identify users who visited pages hosting exploit payloads
  • Hunt for post-exploitation behaviors such as script interpreters or LOLBins spawned by browser processes

Monitoring Recommendations

  • Enable renderer crash reporting and forward crash dumps to a central analytics pipeline
  • Alert on Chrome processes writing to or executing from user-writable directories
  • Track browser version drift continuously using endpoint management tooling
  • Review DNS and TLS logs for connections to domains serving unsolicited HTML redirects

How to Mitigate CVE-2026-113019

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
  • Force-restart Chrome after update deployment to ensure the patched binary is loaded
  • Audit Chromium-based browsers and embedded webviews for vendor patches incorporating the fix
  • Restrict access to high-risk browsing categories for users who cannot immediately update

Patch Information

Google addressed the vulnerability in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. Administrators should deploy Chrome 156.0.8078.47 or newer through enterprise update channels such as Google Update, SCCM, Intune, or Jamf. Chromium-based browsers including Edge, Brave, Opera, and Vivaldi require separate vendor updates once upstream fixes are merged.

Workarounds

  • No official workaround removes the vulnerability without applying the Chrome update
  • Deploy enterprise policies that enforce site isolation and block execution of untrusted scripts where feasible
  • Use web filtering to block known-malicious domains and reduce exposure to crafted HTML payloads
  • Consider temporarily routing high-risk users through a remote browser isolation solution until patching completes
bash
# Verify installed Chrome version on Windows
reg query "HKLM\SOFTWARE\Google\Chrome\BLBeacon" /v version

# Verify installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version

# Verify installed Chrome version on Linux
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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.