CVE-2026-87505: Google Google Chrome vulnerability

Q: 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.

Q: 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.

Q: 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.

Published Sep 9, 2026

Updated

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)

Affected Software

1 affected component

Google Google Chrome<153.0.8010.36

Event History

Sep 9, 2026

CVE Published

via MITRE·12:09 AM

Data Sourced

via MITRE·12:09 AM

DescriptionWeakness

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.