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

CVE-2026-113061: Google Chrome Chromoting RCE Vulnerability

CVE-2026-113061 is a memory corruption flaw in Google Chrome Chromoting that enables remote attackers to execute arbitrary code within the sandbox via malicious HTML pages. This article covers technical details, affected versions, security impact, and recommended 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-113061 Overview

CVE-2026-113061 is a memory corruption vulnerability in the Chromoting component of Google Chrome, the browser's remote desktop functionality. The flaw affects Chrome versions prior to 156.0.8078.47 on desktop platforms. A remote attacker can trigger memory corruption through a crafted HTML page, potentially achieving arbitrary code execution inside the Chrome sandbox. Exploitation requires user interaction, such as visiting a malicious webpage. The vulnerability is tracked under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer. Google rated the Chromium security severity as Low, while NVD assigned a higher CVSS score reflecting the potential for arbitrary code execution.

Critical Impact

A remote attacker can execute arbitrary code within the Chrome sandbox by luring a user to a crafted HTML page.

Affected Products

  • Google Chrome Desktop versions prior to 156.0.8078.47
  • Chromoting (Chrome Remote Desktop) component
  • Chromium-based browsers incorporating the vulnerable Chromoting code

Discovery Timeline

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

Technical Details for CVE-2026-113061

Vulnerability Analysis

The vulnerability resides in Chromoting, the Chrome subsystem supporting Chrome Remote Desktop sessions. Memory corruption occurs when the component processes attacker-controlled data from a crafted HTML page. An attacker who successfully exploits the flaw can execute arbitrary code within the renderer sandbox boundary. Exploitation chains that include a sandbox escape could extend the impact to the host operating system.

The network attack vector requires only that a user visit or load content from an attacker-controlled page. Exploitation does not require authentication, which lowers the barrier for drive-by compromise campaigns. The affected code path overlaps with features exposed to web content, making the issue reachable from standard browsing contexts.

Root Cause

The underlying weakness is classified as CWE-119, covering improper restriction of operations within memory buffer bounds. Memory corruption of this class typically arises from missing length checks, incorrect pointer arithmetic, or type confusion during parsing or object handling. Google has not publicly disclosed the exact faulty function. Refer to the Chromium Issue Tracker Entry for implementation details once Google removes the embargo.

Attack Vector

Exploitation begins when a user loads a crafted HTML page in a vulnerable Chrome build. The page delivers JavaScript or markup that interacts with Chromoting code paths to trigger the corruption. Successful exploitation yields arbitrary code execution inside the Chrome sandbox. Combined with a separate sandbox escape, the chain could lead to full browser or host compromise. See the Google Chrome Update Announcement for Google's official description.

No public proof-of-concept exploit is available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The current EPSS probability is 0.406%.

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-113061

Indicators of Compromise

  • Chrome processes crashing or exhibiting abnormal memory faults in chromoting-related modules.
  • Unexpected child processes spawned by chrome.exe or renderer processes immediately after visiting an unfamiliar site.
  • Outbound connections from Chrome renderer processes to untrusted hosts following page loads.
  • Browser telemetry showing Chrome version strings below 156.0.8078.47 after the patch window.

Detection Strategies

  • Deploy endpoint behavioral analytics to flag renderer process anomalies, including unexpected code execution and child process creation.
  • Inventory Chrome versions across the fleet using software asset management or EDR telemetry and alert on versions earlier than 156.0.8078.47.
  • Inspect proxy and DNS logs for user navigation to newly observed or low-reputation domains preceding Chrome crashes.

Monitoring Recommendations

  • Enable crash reporting and forward Chrome crash dumps to a central analysis pipeline for triage.
  • Monitor Windows Event Logs, macOS Unified Logs, and Linux journald for repeated Chrome process termination events.
  • Correlate browser crash events with network traffic to identify potential exploitation attempts.

How to Mitigate CVE-2026-113061

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later across all desktop endpoints.
  • Verify that automatic updates are enabled and that managed deployments are not pinned to older channels.
  • Restart Chrome on all endpoints after the update to ensure the patched binaries are loaded.

Patch Information

Google released the fix in Chrome stable channel version 156.0.8078.47. Patch details and release notes are available in the Google Chrome Update Announcement. Enterprise administrators should push the update through group policy, Jamf, Intune, or equivalent management tooling.

Workarounds

  • Disable or restrict access to Chrome Remote Desktop features where business requirements allow.
  • Enforce enterprise browser policies that block navigation to untrusted or uncategorized sites until patching completes.
  • Apply site isolation and strict sandbox policies through Chrome Enterprise policy templates.
bash
# Verify Chrome version on Linux/macOS endpoints
google-chrome --version

# Example Chrome Enterprise policy snippet (JSON) to force update channel
{
  "TargetChannel": "stable",
  "ChromeVariations": 2,
  "RemoteAccessHostFirewallTraversal": false
}

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.