CVE-2026-87505: Google Chrome FileSystem Auth Bypass Flaw

CVE-2026-87505 Overview

CVE-2026-87505 is an incorrect authorization vulnerability [CWE-863] in the FileSystem component of Google Chrome versions prior to 153.0.8010.36. A remote attacker who has already compromised the renderer process can use a crafted PDF file to bypass Chrome's site isolation boundary. Site isolation is the security architecture that keeps content from different origins in separate processes. Bypassing it enables cross-origin data access that should otherwise be blocked by the browser sandbox model. Chromium rates the security severity as Medium, while the NVD assigns a High CVSS score reflecting the confidentiality and integrity impact.

Critical Impact

An attacker with a compromised renderer can escape site isolation using a crafted PDF, exposing data from other origins loaded in the browser.

Affected Products

• Google Chrome Desktop versions prior to 153.0.8010.36
• Chromium-based browsers incorporating the vulnerable FileSystem component
• All operating system builds of Chrome Stable channel before the fixed release

Discovery Timeline

• 2026-09-09 - CVE-2026-87505 published to NVD
• 2026-09-10 - Last updated in NVD database

Technical Details for CVE-2026-87505

Vulnerability Analysis

The flaw resides in Chrome's FileSystem implementation, where authorization checks fail to properly enforce site isolation boundaries when handling a crafted PDF. Site isolation places documents from different sites into distinct renderer processes so that a compromise of one renderer cannot read data belonging to another. The incorrect authorization allows a renderer that an attacker already controls to reach data or perform actions associated with a different origin. Exploitation requires two conditions: prior compromise of the renderer process and user interaction to load the malicious PDF. Chained with a renderer exploit, this weakness escalates the impact from single-origin compromise to cross-origin data exposure.

Root Cause

The root cause is an authorization check in the FileSystem component that does not correctly validate the calling origin against site isolation policy. Because the check is performed within the browser process on behalf of a renderer, incorrect enforcement allows a malicious renderer to request operations outside its assigned site boundary. This is a classic [CWE-863] Incorrect Authorization weakness surfacing at a security boundary that Chrome relies on for multi-origin isolation.

Attack Vector

The attack chain begins with a renderer compromise, typically achieved by exploiting a separate memory-safety issue through a malicious web page. The attacker then serves a crafted PDF that triggers the FileSystem code path with parameters that pass the flawed authorization check. Once the check is bypassed, the compromised renderer performs actions or accesses data associated with another site loaded in the browser. Network delivery combined with required user interaction to open or render the PDF completes the exploitation path.

No public proof-of-concept code is available. Refer to the Chromium Issue Tracker #517597701 and the Chrome Blog Update Announcement for additional technical context once access restrictions are lifted.

Detection Methods for CVE-2026-87505

Indicators of Compromise

• Chrome browser processes rendering unsolicited PDF content from untrusted origins immediately after visiting a suspicious page
• Unexpected cross-origin FileSystem API activity in browser telemetry preceding data exfiltration attempts
• Chrome Stable installations reporting versions earlier than 153.0.8010.36 in endpoint inventory

Detection Strategies

• Inventory Chrome versions across managed endpoints and flag any build earlier than 153.0.8010.36 as vulnerable
• Correlate renderer process crashes and PDF rendering events with subsequent outbound network activity indicative of data staging
• Monitor for exploit chains that first establish renderer compromise, since this vulnerability requires that prerequisite

Monitoring Recommendations

• Ingest browser and endpoint process telemetry into a centralized data lake for cross-source correlation of PDF-triggered anomalies
• Alert on Chrome child processes spawning unexpected file access patterns or interacting with cross-origin resources
• Track patch compliance against Chrome Stable channel release notes to identify drift on unmanaged or BYOD devices

How to Mitigate CVE-2026-87505

Immediate Actions Required

• Update Google Chrome to version 153.0.8010.36 or later on all Windows, macOS, and Linux endpoints
• Restart Chrome after applying the update to ensure the patched binary is loaded across all sessions
• Verify enterprise deployment tooling has pushed the update to remote and offline devices as they reconnect

Patch Information

Google released the fix in the Chrome Stable channel version 153.0.8010.36. Details are published in the Chrome Blog Update Announcement. Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi should be updated to versions that incorporate the corresponding Chromium fix.

Workarounds

• Disable Chrome's built-in PDF viewer via enterprise policy and route PDFs to a hardened external viewer until patching completes
• Restrict untrusted PDF downloads and inline rendering through web filtering or content disarm and reconstruction controls
• Enforce Chrome auto-update through group policy or MDM to shorten exposure windows for future browser vulnerabilities

# Verify installed Chrome version on Linux/macOS
google-chrome --version

# Windows PowerShell: check installed Chrome version
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion

# Chrome enterprise policy to disable built-in PDF viewer (Linux example)
# /etc/opt/chrome/policies/managed/disable_pdf.json
{
  "AlwaysOpenPdfExternally": true
}