CVE-2026-13806: Chrome Site Isolation Bypass via Accessibility Vulnerability

Technical summary

The vulnerability stems from insufficient input validation in Chrome's Accessibility subsystem (CWE-20). An attacker with control over the renderer process can craft a malicious HTML page that exploits this validation gap to escape site isolation boundaries. Site isolation operates as a trust boundary in Chrome's architecture; when this boundary is breached, the security model that prevents cross-site data leakage fails. The attack requires renderer-level compromise as a prerequisite, meaning the attacker must already have code execution within Chrome's sandbox, but the vulnerability then allows lateral movement to other isolated sites.

Business impact

For enterprises, this vulnerability affects the confidentiality guarantees that Chrome's site isolation provides. Users who are targets of sophisticated attacks—such as employees at high-value organizations—could have sensitive information stolen from one website while viewing another. The attack chain requires initial compromise of the renderer sandbox, so it is primarily a risk in targeted scenarios rather than mass exploitation. However, when combined with other vulnerabilities, it could enable complete information theft across multiple websites visited in the same browser session.

Affected systems

Google Chrome prior to version 150.0.7871.47 is affected across all operating systems that Chrome supports (Windows, macOS, Linux, Android, iOS). Any organization or individual using Chrome versions before the fixed release is at risk. Chrome's auto-update mechanism typically delivers patches within days, but devices with disabled updates or users who defer updates remain exposed.

Exploitability

Exploitability requires two sequential events: first, the renderer process must already be compromised through another vulnerability or attack vector; second, the user must visit a malicious HTML page while that compromise is active. The CVSS score of 8.1 reflects the high impact (confidentiality and integrity compromise) balanced against the non-trivial prerequisite of renderer compromise. This is not a trivial drive-by attack; it is a post-compromise technique for attackers who have already gained a foothold in the browser process. The user interaction requirement (UI:R) also implies social engineering or targeted delivery of the malicious page.

Remediation

Update Google Chrome to version 150.0.7871.47 or later. Chrome's automatic update system should deliver this patch to most users within a few days of release. Organizations can verify the installed version at chrome://version/ and manually trigger updates through Settings > About Google Chrome. For managed environments, administrators should use Chrome Enterprise policies to enforce automatic updates and verify compliance across their fleet.

Patch guidance

Verify that Chrome has updated to 150.0.7871.47 or later by navigating to chrome://version/. On macOS and Windows, restart Chrome or the system to complete the update if prompted. For Android, update through the Google Play Store. For iOS, update through the App Store. Enterprise administrators should confirm deployment via Chrome management console and monitor for successful rollout to all managed devices. If auto-update is disabled in your environment, manually deploy the patch through your software distribution system.

Detection guidance

Detection is challenging because the vulnerability operates within the browser's process model and requires pre-existing renderer compromise. Monitor for unusual process behavior in Chrome, such as unexpected child processes or system calls that suggest sandbox escape. Network detection is unlikely to reveal exploitation unless the malicious HTML is served from a monitored gateway. Focus instead on identifying initial renderer compromise through endpoint detection tools that monitor for code execution within browser processes. Retrospective detection of site isolation bypass would require browser forensics or memory analysis, which is impractical at scale.

Why prioritize this

This vulnerability should be patched promptly because it eliminates a critical defense mechanism in Chrome—site isolation—once the renderer is compromised. While the attack requires a prerequisite compromise, organizations with high-value targets (finance, defense, intelligence, media) should treat it as a priority. The high CVSS score and confidentiality impact justify rapid patching. However, it is not an emergency patch for all users; rather, it is a standard high-priority security update that should be deployed within your normal patch cycle (typically 1–2 weeks).

Risk score, explained

The CVSS 3.1 score of 8.1 (HIGH) is derived from: high confidentiality impact (the attacker can read data from other sites), high integrity impact (the attacker can modify data), low attack complexity (no special conditions beyond the prerequisite), network-based attack vector, and a user interaction requirement. The score does not account for the renderer compromise prerequisite, which would lower real-world exploitability; CVSS assumes the attacker can reach the vulnerable code. The severity reflects the gravity of breaking site isolation once an attacker has the required foothold.

Frequently asked questions