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

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

CVE-2026-113141 is a use after free vulnerability in Google Chrome Transactions Platform that allows remote attackers to execute arbitrary code within the sandbox. This post explains its impact, affected versions, and mitigation steps.

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

CVE-2026-113141 is a use-after-free vulnerability [CWE-416] in the Transactions Platform 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 renderer sandbox. Google's Chromium team rated the issue High severity. The vulnerability requires user interaction, specifically visiting an attacker-controlled page.

Critical Impact

Remote attackers can achieve arbitrary code execution within the Chrome sandbox by luring users to a malicious HTML page, providing a foothold for further sandbox escape chains.

Affected Products

  • Google Chrome Desktop versions prior to 156.0.8078.47
  • Chromium-based builds that incorporate the vulnerable Transactions Platform code
  • Downstream browsers that embed the affected Chromium release branch

Discovery Timeline

  • 2026-10-20 - CVE-2026-113141 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-113141

Vulnerability Analysis

The vulnerability resides in Chrome's Transactions Platform, a component responsible for coordinating browser-mediated transactional workflows. A use-after-free condition occurs when code continues to reference a heap object after its backing memory has been released. An attacker who controls the lifecycle of the freed object can place attacker-controlled data at the same allocation, causing the dangling pointer to operate on malicious contents.

When the browser dereferences the stale pointer, control flow or data flow can be redirected. In the context of a renderer-process bug, this typically yields arbitrary read/write primitives followed by arbitrary code execution within the sandboxed renderer. The attacker still operates inside the Chrome sandbox, meaning follow-on sandbox escape vulnerabilities are usually required to compromise the host system.

Root Cause

The root cause is improper object lifetime management in the Transactions Platform [CWE-416]. A reference to a transaction-related object is retained and later dereferenced after the object has been freed. Race conditions between asynchronous callbacks and object destruction frequently underlie such defects in Chromium.

Attack Vector

The attack vector is network-based and requires user interaction. The victim must load a crafted HTML page delivered through phishing, malvertising, a compromised website, or an embedded iframe. No authentication or prior access is required. Once the page triggers the vulnerable code path, the attacker gains code execution in the renderer process.

No verified public proof-of-concept is available. See the Chromium Issue Tracker Entry and the Google Chrome Desktop Update for vendor details.

Detection Methods for CVE-2026-113141

Indicators of Compromise

  • Chrome renderer processes spawning unexpected child processes such as cmd.exe, powershell.exe, or shell interpreters.
  • Outbound connections from Chrome to unfamiliar domains immediately after loading an unknown page.
  • Renderer process crashes with heap corruption signatures recorded in chrome_debug.log or Windows WER reports.

Detection Strategies

  • Inventory installed Chrome versions across the fleet and flag any build older than 156.0.8078.47.
  • Monitor endpoint telemetry for anomalous process trees originating from chrome.exe renderer processes.
  • Correlate web proxy logs with threat intelligence to identify users accessing pages hosting exploit content.

Monitoring Recommendations

  • Enable browser crash reporting and forward Chrome crash telemetry to centralized logging for triage.
  • Alert on child process creation from Chrome renderers that is not part of expected plug-in or helper activity.
  • Track memory region anomalies and executable allocation patterns on endpoints running Chrome.

How to Mitigate CVE-2026-113141

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints.
  • Validate that automatic updates are enabled and successfully completing on Windows, macOS, and Linux clients.
  • Restart Chrome after the update to ensure the patched binary is loaded into memory.

Patch Information

Google addressed CVE-2026-113141 in the Chrome Stable channel release documented in the Google Chrome Desktop Update. Administrators should deploy Chrome 156.0.8078.47 or newer. Enterprise deployments can enforce the update through the RelaunchNotification and RelaunchNotificationPeriod Chrome policies to force a timely restart.

Workarounds

  • Restrict browsing to trusted sites via web proxy allowlists until patching is complete.
  • Enforce Chrome Site Isolation and strict renderer sandboxing through enterprise policy.
  • Deploy script and ad blocking at the network edge to reduce exposure to crafted HTML payloads.
bash
# Example: enforce Chrome relaunch after update via group policy (Windows)
reg add "HKLM\Software\Policies\Google\Chrome" /v RelaunchNotification /t REG_DWORD /d 2 /f
reg add "HKLM\Software\Policies\Google\Chrome" /v RelaunchNotificationPeriod /t REG_DWORD /d 86400000 /f

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.