CVE-2026-11151: Google Chrome Password Manager Sandbox Escape Vulnerability

Technical summary

CVE-2026-11151 stems from insufficient input validation (CWE-20) in Chrome's Password Manager when handling untrusted data. The vulnerability exists in Chrome versions prior to 149.0.7827.53. An attacker with an already-compromised renderer process can craft a specially designed HTML page that exploits this validation gap to achieve sandbox escape. The Chromium project classified this as medium severity at the component level, though the CVSS 3.1 base score reflects a higher risk due to the confidentiality, integrity, and availability impact of successful exploitation.

Business impact

A successful exploit chains renderer compromise with sandbox escape, giving an attacker system-level access. This could lead to theft of stored passwords and sensitive data managed by Chrome's Password Manager, lateral movement within the system, installation of persistent malware, or compromise of other user applications. Organizations relying on Chrome in regulated environments face potential data breach notifications and compliance violations. The attack requires user interaction (visiting a malicious page) but assumes the attacker already controls the renderer—a realistic scenario in drive-by download or watering-hole campaigns.

Affected systems

Google Chrome on Windows, macOS, and Linux is directly affected. All versions prior to 149.0.7827.53 are vulnerable. Organizations using Chrome as a primary browser, especially those with users working in high-risk environments, should prioritize patching. The vulnerability affects Chrome on all supported operating systems (Windows, macOS, and Linux).

Exploitability

This vulnerability requires a two-stage attack: first, compromise of the Chrome renderer process (via a separate vulnerability or attack vector), then exploitation of this input validation flaw to escape the sandbox. While the CVSS vector indicates user interaction is needed (UI:R), that refers to visiting a malicious page—a lower bar than many exploits. However, the prerequisite renderer compromise limits real-world frequency compared to single-stage renderer bugs. Exploitation complexity is high (AC:H), reflecting the technical skill needed to chain attacks or find a renderer gadget. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities catalog.

Remediation

Update Google Chrome to version 149.0.7827.53 or later. Chrome automatically updates in the background on most systems, but users should verify they are running the latest version by navigating to Chrome menu > About Google Chrome. Organizations managing Chrome via enterprise policies should deploy the patch through their device management solution. No workarounds exist; patching is the only mitigation.

Patch guidance

Priority should be given to endpoints where Chrome is the primary browser or where users frequently visit untrusted websites. Test the patch in a non-critical environment first to ensure no compatibility issues with internal web applications or extensions. Consider using Chrome's enterprise policies (like 'Update' policies) to enforce timely patching across the organization. Verify successful deployment by confirming all managed Chrome instances report version 149.0.7827.53 or higher within 7–14 days of availability.

Detection guidance

Monitor Chrome process behavior for signs of sandbox escape, including unexpected system calls, file system access from the renderer process, or creation of privileged child processes. Network detection is limited since exploitation occurs post-compromise; focus on behavioral analytics that flag anomalous renderer activity. Log and alert on visits to known malicious domains or suspicious HTML-serving sites. In a post-incident scenario, examine Chrome's crash reports and sandbox violation logs via Chrome's internal debugging features. Endpoint Detection and Response (EDR) tools should be tuned to alert on cross-process access patterns that indicate sandbox bypass.

Why prioritize this

Although not yet exploited in the wild (KEV status: No), this vulnerability bridges renderer compromise to system-level access, making it a critical stepping stone in multi-stage attacks. The Password Manager context is particularly sensitive due to stored credentials. The CVSS score of 7.5 (HIGH) and the user-interaction requirement should not delay patching, especially for organizations in sectors targeted by browser-based attacks. The high AC value reflects technical complexity, not low priority—sandbox escape bugs are prized by sophisticated attackers. Patch within 30 days of release as a baseline; critical environments should patch sooner.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects High impact across confidentiality, integrity, and availability (C:H/I:H/A:H), tempered by high attack complexity (AC:H) and the requirement for user interaction (UI:R). Attack vector is network-based (AV:N), and the scope is unchanged (S:U). The high AC and UI requirements prevent a Critical rating, but the full system compromise potential—once the renderer is compromised—justifies a HIGH severity score. Organizations should treat this as a higher priority than the Chromium medium classification suggests, due to the privilege escalation aspect.

Frequently asked questions