CVE-2026-13849: Chrome Chromoting Sandbox Escape via Malicious File

Technical summary

CVE-2026-13849 stems from insufficient input validation in Chromoting, Google Chrome's remote desktop capability. The flaw allows a local attacker to craft a malicious file that, when processed by Chrome, bypasses sandbox protections due to CWE-20 (improper input validation). The attack requires user interaction (opening a file) but no special privileges, making it accessible to any local actor on a Windows system. Once the sandbox is escaped, an attacker gains arbitrary code execution with the privileges of the Chrome process.

Business impact

This vulnerability poses a significant risk to organizations where users have local administrative or standard-user access on Windows machines running Chrome. Successful exploitation could allow malicious actors to move laterally within a network, steal credentials or sensitive data, deploy malware, or gain persistent footholds. For businesses relying on Chrome for critical workflows or those with strict isolation requirements, this represents a material increase in local privilege escalation risk until patching is complete.

Affected systems

Google Chrome on Microsoft Windows systems running version 149.0.7871.46 and earlier are vulnerable. The vulnerability does not affect Chrome on macOS, Linux, or other platforms, nor does it impact other browsers. Windows administrators should prioritize Chrome inventory across their environment to identify exposed instances.

Exploitability

While this flaw requires local access and user interaction (opening a malicious file), these are not substantial barriers in typical corporate environments where users can download and open files. No public exploit code is currently known to exist, and the vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog. However, the simplicity of the attack vector and high impact make it an attractive target for future weaponization, particularly in supply-chain or targeted campaigns.

Remediation

The primary mitigation is to upgrade Google Chrome to version 150.0.7871.47 or later on all Windows systems. Administrators should enable automatic updates to ensure users receive patches promptly. As a temporary measure, restrict the execution of downloaded files by untrusted sources and educate users on the risks of opening unexpected attachments or files from unfamiliar origins.

Patch guidance

Deploy Chrome version 150.0.7871.47 or newer across your Windows environment. Google Chrome's auto-update mechanism will distribute the patch, but administrators managing enterprise deployments should verify patch application through their deployment tools. Verify the update through Chrome's About page (Menu → About Google Chrome) which displays the current version. For managed deployments via Google Chrome Enterprise or similar tools, test patches in a pilot environment before full rollout to ensure compatibility with your organization's extensions and configurations.

Detection guidance

Monitor for unusual file-opening activity in Chrome, particularly files originating from external sources or downloads folders. Look for Chrome processes spawning unexpected child processes—a sign of sandbox escape. Endpoint detection and response (EDR) solutions should flag Chrome executing system commands or accessing sensitive files outside its normal scope. Review logs for failed Chrome updates or systems lagging behind the current version; prioritize those machines for manual patching and investigation.

Why prioritize this

This vulnerability merits high-priority patching due to the combination of high CVSS score (8.6), local attack surface in virtually all Windows environments, and the severity of sandbox escape. While not yet publicly exploited, the low complexity and user-interaction requirement make it a natural candidate for future adversary tooling. Given the ease of patch deployment and the critical nature of the impact, this should be addressed within 7–14 days.

Risk score, explained

The CVSS 3.1 score of 8.6 (HIGH) reflects the confluence of local attack vector, low attack complexity, no privilege requirement, and consequences affecting confidentiality, integrity, and availability across system boundaries. The score would be higher if the vulnerability required no user interaction; however, the reliance on user action (opening a file) prevents a critical rating. In practice, the human element is often the weakest link, reducing the distinction between this and a network-based critical flaw.

Frequently asked questions