CVE-2026-87652: Google Chrome vulnerability

Q: What must an attacker achieve before exploiting this issue?

The attacker must first compromise the Chrome renderer process. The bypass is then triggered through a crafted HTML page.

Q: What security boundary can be bypassed?

A compromised renderer can bypass the web origin policy through incorrect authorization in PushAPI.

Q: Which Chrome versions need to be updated?

Google Chrome versions prior to 153.0.8010.36 are affected. Updating to 153.0.8010.36 or later addresses the affected version range.

Published Sep 9, 2026

Updated

Incorrect authorization in PushAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)

Affected Software

1 affected component

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 must an attacker achieve before exploiting this issue?

The attacker must first compromise the Chrome renderer process. The bypass is then triggered through a crafted HTML page.

What security boundary can be bypassed?

A compromised renderer can bypass the web origin policy through incorrect authorization in PushAPI.

Which Chrome versions need to be updated?

Google Chrome versions prior to 153.0.8010.36 are affected. Updating to 153.0.8010.36 or later addresses the affected version range.