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

CVE-2026-113289: Google Chrome PerformanceAPIs RCE Flaw

CVE-2026-113289 is a remote code execution vulnerability in Google Chrome PerformanceAPIs caused by improper input validation. Attackers can execute arbitrary code in the sandbox via malicious HTML pages. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

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

CVE-2026-113289 is an improper input validation vulnerability [CWE-20] in the PerformanceAPIs component of Google Chrome. Versions prior to 156.0.8078.47 fail to properly validate input, which allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. Exploitation requires the victim to load a crafted HTML page. Google tracked the issue through Chromium Issue Tracker #511311494 and addressed it in the Chrome Stable Channel Update.

Critical Impact

A single visit to a malicious website can trigger arbitrary code execution inside the Chrome renderer sandbox, giving attackers a foothold for sandbox escape chains and further compromise.

Affected Products

  • Google Chrome Desktop versions prior to 156.0.8078.47
  • Chromium-based browsers that ship the vulnerable PerformanceAPIs code
  • Embedded applications using Chromium builds older than release 156

Discovery Timeline

  • 2026-10-20 - CVE-2026-113289 published to the National Vulnerability Database
  • 2026-10-21 - Entry last modified in the NVD database

Technical Details for CVE-2026-113289

Vulnerability Analysis

The flaw resides in Chrome's PerformanceAPIs implementation, which exposes performance measurement interfaces to web content. The component fails to properly validate input supplied through these APIs. An attacker who controls page content can supply crafted values that bypass expected constraints and corrupt internal state inside the renderer process.

Successful exploitation allows arbitrary code execution within the Chrome sandbox. While the sandbox limits direct host impact, renderer code execution is routinely chained with additional vulnerabilities to achieve full sandbox escape. Google classified the Chromium security severity as Medium, while the NVD assigned a higher score reflecting network reach and impact to confidentiality, integrity, and availability.

Root Cause

The root cause is improper input validation [CWE-20] in the PerformanceAPIs interface. The code path accepts attacker-influenced values from JavaScript without enforcing the type, range, or structural checks required to safely process them. Downstream logic then operates on malformed data, resulting in memory or control-flow corruption that attackers can shape into code execution.

Attack Vector

Exploitation is remote and requires user interaction. A victim must visit or be redirected to a page controlled by the attacker. Delivery vectors include phishing links, malvertising, compromised legitimate sites, and iframes embedded in trusted content. No authentication is required, and the exploit executes entirely within the browser process when the page loads JavaScript that invokes the vulnerable PerformanceAPIs methods.

No public proof-of-concept code is available in the referenced sources. See Chromium Issue Tracker #511311494 for restricted technical details.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-113289

Indicators of Compromise

  • Chrome renderer processes spawning unexpected child processes or performing unusual file writes shortly after browsing activity
  • Outbound network connections from chrome.exe to newly observed or low-reputation domains following page loads
  • Browser crash telemetry referencing PerformanceAPIs or performance measurement code paths

Detection Strategies

  • Inventory installed Chrome versions across the fleet and flag any instance below 156.0.8078.47
  • Hunt for HTML or JavaScript artifacts that invoke performance.mark, performance.measure, or related APIs with abnormal or oversized arguments
  • Correlate browser process anomalies with proxy and DNS logs to identify suspected exploitation chains

Monitoring Recommendations

  • Enable endpoint telemetry on browser process trees, child process creation, and script interpreter launches
  • Forward browser crash reports and renderer sandbox violations to the SIEM for review
  • Monitor web proxy logs for user agents still reporting pre-156 Chrome builds after the patch rollout window

How to Mitigate CVE-2026-113289

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
  • Restart browser sessions after patching to ensure the updated binaries are loaded
  • Audit Chromium-based applications and embedded browsers for the vulnerable component and patch to the fixed Chromium release

Patch Information

Google released the fix in the Chrome Stable Channel update documented in the Chrome Stable Channel Update. Administrators should confirm the installed version is 156.0.8078.47 or later. Enterprise deployments using managed update channels should validate that Chrome auto-update is enabled and that policy settings do not block the rollout.

Workarounds

  • Enforce enterprise policy to require the patched Chrome version and block launch of outdated builds
  • Restrict browsing to trusted sites via web filtering until all endpoints are patched
  • Disable or restrict JavaScript on untrusted sites using Chrome enterprise policies where feasible
bash
# Verify Chrome version on Linux/macOS
google-chrome --version

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

# Enterprise policy: force minimum version via Chrome policy
# (Linux example at /etc/opt/chrome/policies/managed/version.json)
{
  "TargetVersionPrefix": "156.0.8078.47",
  "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

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.