CVE-2026-12460: Chrome Site Isolation Bypass via Crafted PDF

Technical summary

The vulnerability stems from insufficient policy enforcement in Chrome's file system access implementation, classified under CWE-284 (Improper Access Control). When a renderer process has been compromised, an attacker can craft a PDF file that, when processed, circumvents the site isolation sandbox boundaries. Site Isolation is Chrome's multi-process architecture feature designed to prevent cross-site data leakage and CSRF attacks by running content from different sites in separate processes. This flaw demonstrates that policy validation for file operations is not consistently enforced at boundaries where isolation should be maintained, allowing a malicious renderer to access resources that should be restricted to other sites.

Business impact

While the CVSS score reflects a medium overall rating, the practical impact depends on existing renderer compromise scenarios. In environments where users access sensitive SaaS applications or internal web tools through Chrome, a successful exploit allows attackers to exfiltrate data across site boundaries after gaining initial renderer access. This bridges the gap between renderer compromise (e.g., from a malicious website or advertisement) and broader data theft. For organizations relying on Chrome's isolation guarantees, this represents a containment failure that could facilitate credential theft, session hijacking, or access to confidential documents from cross-origin applications.

Affected systems

Google Chrome on all major platforms (Windows, macOS, and Linux) running versions prior to 149.0.7827.155 are affected. The vulnerability is platform-agnostic; Site Isolation operates identically across Chrome's supported operating systems. Organizations using Chrome as a primary browser for accessing web applications should treat this as broadly applicable.

Exploitability

Exploitation requires two preconditions: the renderer process must already be compromised through another attack vector (such as a malicious website, drive-by download, or malvertisement), and the user must interact with the malicious PDF file. The CVSS vector (AC:H, UI:R) reflects this complexity. While not trivial, it represents a realistic follow-on attack in breach scenarios. An attacker controlling a compromised website could serve the crafted PDF to redirect the renderer's access capabilities. The scenario is credible in targeted attacks against high-value users or in coordinated campaigns following initial web-based compromise.

Remediation

Update Google Chrome to version 149.0.7827.155 or later. This patch restores proper policy enforcement for file system access within the renderer process sandbox. Automatic updates are enabled by default in Chrome; however, security teams should verify deployment across managed endpoints using Chrome enterprise policies or endpoint management solutions. No workaround exists short of updating; disabling PDF viewing is impractical and not recommended.

Patch guidance

Deploy Chrome version 149.0.7827.155 or newer across all managed devices. Use Google Chrome Enterprise tools (such as Google Admin Console or third-party MDM solutions) to enforce minimum version requirements. Test the update in a small pilot group before full rollout if your environment has strict compatibility requirements, though this patch is routine maintenance. Chrome's auto-update mechanism can be trusted for unmanaged user devices, but verify that managed devices do not have update policies that would delay deployment. Check Chrome's release notes to confirm this fix is included in the version being deployed.

Detection guidance

Detection requires behavioral monitoring rather than signature-based approaches, as the exploit involves crafted PDF content within an already-compromised renderer. Log Chrome crash reports and renderer process terminations, which may indicate exploitation attempts. Monitor for unusual file access patterns from Chrome processes, particularly cross-origin PDF handling. Endpoint Detection and Response (EDR) tools should flag suspicious interactions between Chrome renderers and file system APIs. Proactive detection is challenging; emphasis should be on reducing renderer compromise risk through browser isolation, content security policies, and blocking of malicious advertisements.

Why prioritize this

This vulnerability should be prioritized as a medium to high business risk despite its CVSS score, because it represents a containment failure in Chrome's core security architecture. Site Isolation is a foundational defense against cross-site attacks; a bypass—even one requiring prior compromise—weakens overall browser security posture. For organizations where Chrome is the primary enterprise browser and users access sensitive applications, the remediation effort is minimal (automatic patching) while the risk reduction is substantial. Prioritize patching in the first week after release; delay beyond two weeks is not justified given the ease of deployment.

Risk score, explained

The CVSS 3.1 score of 4.2 (MEDIUM) reflects the requirement for both renderer compromise (AC:H) and user interaction with a crafted PDF (UI:R), which correctly limits the score. However, this numerical rating undersells the strategic importance of the flaw: a Site Isolation bypass has historical significance in browser security, even when constrained. The confidentiality and integrity impacts (C:L, I:L) are accurate but modest—the attacker can read and modify cross-site data rather than achieve full system compromise. Organizations should interpret this as a 'medium CVSS, high priority' scenario due to patch simplicity and architectural importance.

Frequently asked questions