CVE-2026-87505: High severity Google Google Chrome vulnerability
Chromium CVE-2026-87505: Incorrect authorization in FileSystem
Other sources
Incorrect authorization in FileSystem in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: Medium)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 153.0.4234.32 - Upgrade
Upgrade
Chrome/Chromium (Chromium-based Edge)to a version that resolves this vulnerability.Fixed in 153.0.8010.36
Event History
Frequently Asked Questions
What does an attacker need before this issue can be exploited?
The attacker must first have compromised the Chrome renderer process. Exploitation then involves a crafted PDF file to bypass site isolation.
Which Chrome versions are affected?
Google Chrome versions prior to 153.0.8010.36 are affected. Updating to 153.0.8010.36 or later addresses the affected version range.
Who is realistically exposed to this vulnerability?
Exposure is limited to Chrome environments where an attacker has already compromised a renderer process and can use a crafted PDF. The issue concerns bypassing Chrome site isolation rather than an initial renderer compromise.