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

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

CVE-2026-113160 is a use-after-free vulnerability in Google Chrome's 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-113160 Overview

CVE-2026-113160 is a use-after-free vulnerability 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 serving a crafted HTML page to a target user. The flaw is tracked as CWE-416: Use After Free and received a Chromium security severity rating of High. Exploitation requires user interaction, specifically visiting an attacker-controlled page. Google addressed the issue in the Stable channel update published through the Google Chrome Stable Update advisory.

Critical Impact

Successful exploitation enables arbitrary code execution inside the Chrome renderer sandbox, providing attackers an initial foothold that can be chained with a sandbox escape for full system compromise.

Affected Products

  • Google Chrome Desktop (Windows, macOS, Linux) prior to 156.0.8078.47
  • Chromium-based browsers incorporating the vulnerable Turbolev component
  • Embedded applications using affected Chromium builds

Discovery Timeline

  • 2026-10-20 - CVE-2026-113160 published to the National Vulnerability Database
  • 2026-10-22 - Entry last modified in NVD

Technical Details for CVE-2026-113160

Vulnerability Analysis

The vulnerability resides in Turbolev, a component within the Chromium rendering pipeline. A use-after-free condition occurs when the component continues to reference memory that has already been freed. An attacker triggers the dangling pointer by serving crafted HTML that manipulates object lifecycles in a specific sequence. Once the freed memory is reclaimed with attacker-controlled data, the browser dereferences it as if it were a valid object.

This primitive gives an attacker control over execution flow inside the renderer process. The renderer runs within the Chrome sandbox, so the immediate impact is scoped to the sandboxed context. Historically, use-after-free bugs in Chrome renderers have been chained with separate sandbox escape vulnerabilities to achieve full remote code execution on the host. The attack requires a victim to visit a malicious or compromised page, satisfying the user interaction requirement.

Root Cause

The root cause is improper object lifetime management within Turbolev. Code paths release an object while another reference remains active, violating the invariants expected by subsequent operations. The condition maps to [CWE-416], a recurring class of defect in C++ codebases that handle complex DOM and task scheduling state.

Attack Vector

Attackers deliver exploitation payloads through standard web channels, including attacker-owned sites, compromised third-party domains, and malvertising. The target must load the crafted HTML page in a vulnerable Chrome build. No credentials or prior access to the victim machine are required.

Technical reproduction details are restricted in the Chromium Issue Report #570203091, consistent with Google's standard practice of withholding specifics until patch adoption increases.

Detection Methods for CVE-2026-113160

Indicators of Compromise

  • Chrome renderer processes spawning unexpected child processes such as cmd.exe, powershell.exe, or shell binaries on Linux and macOS
  • Browser processes writing executable content to user-writable directories or launching persistence mechanisms
  • Outbound connections from chrome.exe to newly registered or low-reputation domains immediately after page loads

Detection Strategies

  • Inventory Chrome installations across the fleet and flag versions earlier than 156.0.8078.47 for prioritized remediation
  • Monitor for anomalous child process creation under browser parent processes, a common post-exploitation signal for renderer compromise
  • Correlate web proxy logs with endpoint telemetry to identify users visiting pages that trigger renderer crashes recorded in Chrome crash dumps

Monitoring Recommendations

  • Collect Chrome crash telemetry and investigate repeated renderer crashes tied to specific URLs
  • Alert on process lineage anomalies where browser renderers execute script interpreters, LOLBins, or write to startup locations
  • Track EPSS trend data for CVE-2026-113160, currently reported at 0.392% with percentile 32.08, and escalate detection coverage if the score rises

How to Mitigate CVE-2026-113160

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all desktop endpoints
  • Restart browser sessions after update deployment to ensure patched binaries are loaded into memory
  • Audit Chromium-derived browsers and Electron-based applications for use of vulnerable Chromium versions and apply vendor updates

Patch Information

Google released the fix in the Stable channel update documented at the Google Chrome Stable Update advisory. Administrators managing Chrome through group policy or MDM should force the update rather than relying on background self-update, especially on endpoints that remain open for extended periods without browser restarts.

Workarounds

  • Enforce browser auto-update policies through enterprise management tools to shrink the exposure window
  • Restrict access to untrusted web content via URL filtering and reputation-based web proxies until patching is confirmed
  • Enable Chrome Site Isolation and ensure the sandbox is not disabled by command-line flags or policy overrides
bash
# Verify installed Chrome version on Linux endpoints
google-chrome --version

# Windows: query the installed version via registry
reg query "HKLM\SOFTWARE\WOW6432Node\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv

# Enforce minimum version via Chrome Enterprise policy (example key)
# Policy: TargetVersionPrefix = "156.0.8078."

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.