CVE-2026-87434: Google Google Chrome vulnerability

Q: What access does an attacker need to exploit this issue?

The attacker must already have compromised the Chrome renderer process and then use a crafted HTML page. The provided information does not indicate that a remote attacker can exploit this vulnerability without renderer-process compromise.

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: What security boundary can be bypassed?

A successful exploit can bypass the web origin policy through missing authorization in CORS. This could allow a compromised renderer to access cross-origin resources contrary to normal browser origin restrictions.

Published Sep 9, 2026

Updated

Missing authorization in CORS 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 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 access does an attacker need to exploit this issue?

The attacker must already have compromised the Chrome renderer process and then use a crafted HTML page. The provided information does not indicate that a remote attacker can exploit this vulnerability without renderer-process compromise.

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.

What security boundary can be bypassed?

A successful exploit can bypass the web origin policy through missing authorization in CORS. This could allow a compromised renderer to access cross-origin resources contrary to normal browser origin restrictions.