CVE-2026-13951: Chrome USB Policy Sandbox Escape (CVSS 8.3)

Technical summary

CVE-2026-13951 is a sandbox escape vulnerability stemming from insufficient policy enforcement in Chrome's USB handling subsystem. The vulnerability requires two preconditions: (1) a compromised renderer process, and (2) user interaction to navigate to a malicious HTML page. The flaw resides in how Chrome validates and restricts USB device access from within the sandbox. An attacker leveraging this could transition from a compromised renderer context to executing code outside the sandbox boundary, potentially gaining full system privileges. The CVSS 3.1 vector reflects the high impact (confidentiality, integrity, availability), though the attack complexity is rated high due to the prerequisite renderer compromise and user interaction requirement.

Business impact

Exploitation could result in complete system compromise for affected users. If an attacker successfully chains this sandbox escape with a renderer vulnerability, they could move from a web-context compromise to arbitrary code execution with system-level privileges. This poses significant risk for organizations where employees browse untrusted content, particularly in environments handling sensitive data. The financial impact includes potential data exfiltration, system downtime, incident response costs, and reputational harm. Users of Chrome in high-risk threat environments should prioritize patching.

Affected systems

Google Chrome versions prior to 150.0.7871.47 are affected. The vulnerability requires a compromised renderer process, meaning it is not exploitable through a single-stage attack vector. Users running Chrome 150.0.7871.47 or later are protected. Organizations should verify their Chrome deployment versions across all managed endpoints, including Windows, macOS, and Linux systems where Chrome is deployed.

Exploitability

While the CVSS score is high (8.3), real-world exploitability requires multiple conditions. An attacker must first compromise the Chrome renderer process—typically via a separate browser vulnerability—and then socially engineer or drive a user to a malicious website. This two-stage requirement significantly limits opportunistic exploitation. However, sophisticated threat actors with access to renderer exploits (either zero-day or known) could combine them with this USB policy bypass to achieve complete sandbox escape. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting no public proof-of-concept has emerged at the time of publication.

Remediation

Immediately update Google Chrome to version 150.0.7871.47 or later. This update is available through Chrome's automatic update mechanism; users can verify their version in Settings > About > Chrome. Organizations should enforce Chrome auto-updates via Group Policy (Windows), Configuration Profiles (macOS), or mobile device management. No workarounds exist; patching is the only mitigation. Additionally, reinforce user security awareness training regarding phishing and malicious websites, since the attack chain requires user interaction.

Patch guidance

Google Chrome delivers patches through its rapid release cycle. Version 150.0.7871.47 or later contains the fix for insufficient USB policy enforcement. Verify the patched version in Chrome's About page, which will display the current version and any pending updates. For enterprise deployments: Windows administrators should enable Chrome auto-update via Group Policy (update_policy_override_platform_minimum = false). macOS administrators can use configuration profiles or manage updates through MDM. Chromebook administrators should ensure automatic updates are enabled in their organization's Chrome Management console. Testing in a small pilot group before broad rollout is recommended to ensure no compatibility issues with internal applications.

Detection guidance

Detecting exploitation is challenging because the attack occurs within the browser sandbox before the escape. Focus on: (1) Monitoring Chrome version compliance across your fleet using endpoint detection and response (EDR) tools or mobile device management; (2) Analyzing browser crash logs for abnormal renderer terminations or sandbox violations; (3) Hunting for suspicious HTML files or phishing campaigns that might carry the initial renderer exploit; (4) Monitoring system calls and process creation from Chrome processes for anomalies post-compromise. Organizations with behavioral threat detection should enable alerts for renderer process escapes or unusual inter-process communication involving Chrome. Host-based indicators are limited until the sandbox is breached, so network-level detection of the malicious webpage delivery is the best preventive signal.

Why prioritize this

Despite being labeled 'Medium' severity by Chromium, the CVSS score of 8.3 (HIGH) and the nature of sandbox escape vulnerabilities warrant immediate prioritization. Sandbox escapes represent a critical elevation in attack capability; a threat actor who successfully exploits this gains near-complete system compromise. The vulnerability's two-stage attack chain—requiring a prior renderer compromise—limits but does not eliminate real-world risk, particularly against targeted high-value users. Organizations should treat this as a critical patching task and complete deployment within days, not weeks.

Risk score, explained

The CVSS 3.1 score of 8.3 reflects: high impact across confidentiality, integrity, and availability (C:H, I:H, A:H); network-based attack vector (AV:N); high attack complexity (AC:H) due to the prerequisite renderer compromise; no privileges required (PR:N); and required user interaction (UI:R). The HIGH severity rating emphasizes the catastrophic potential if all preconditions are met. The gap between Chromium's internal 'Medium' classification and CVSS's 8.3 likely stems from Chromium's view that renderer compromise is itself a significant barrier; however, from a standalone vulnerability perspective, the sandbox escape capability is inherently high-risk because it unlocks system-level access.

Frequently asked questions