CVE-2026-11070: Insufficient validation of untrusted input in Chromoting in Google Chrome on Windows prior to 149

Synopsis

This is an insufficient input validation vulnerability in the Chromoting component of Google Chrome on Windows, affecting versions prior to 149.0.7827.53. The flaw is reachable over the network without authentication, but requires a user to interact with a browser session and assumes the attacker has already compromised the network process. Successful exploitation allows a full sandbox escape, giving the attacker high-impact read, write, and denial-of-service capabilities outside the Chrome sandbox. A patched-image rebuild at version 149.0.7827.53 is available on HarborGuard for affected environments.

HarborGuard Coverage

Exploit Conditions

• Network reachabilityRequired

  The attacker must reach the target over the network, as the vulnerability is exposed through network traffic processed by Chrome's network process.

• AuthenticationNot required

  No credentials or account are needed; the attacker can send malicious network traffic without authenticating to the target.

• Victim interactionRequired

  A user must be actively running a Chrome session that processes the attacker's malicious network traffic, implying a social-engineering or session-hijacking setup is needed to put the victim in reach.

• Attack complexityDetail

  Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, specific memory layouts, or other unpredictable environmental factors, though it does require a prior network process compromise as a precondition.

Blast Radius

• An attacker escapes the Chrome sandbox entirely, gaining code execution outside the browser's isolated process on the Windows host.
• Confidential data accessible to the host user process, including stored credentials, session tokens, and local files, becomes readable.
• The attacker can write or modify files and data on the host, tampering with application state or planting persistent access.
• The attacker can crash or disrupt the host-level process, causing denial of service to the affected workload.