CVE-2026-87543: Google Google Chrome vulnerability

Q: What access does an attacker need before exploiting this issue?

The attacker must already have compromised the Chrome renderer process. The issue is then exploitable remotely using a crafted HTML page to bypass site isolation.

Q: Which Chrome versions are affected?

Google Chrome versions prior to 153.0.8010.36 are affected.

Q: Are users exposed simply by visiting a malicious page?

The available information does not describe this as a standalone drive-by issue: renderer-process compromise is a stated prerequisite. A crafted HTML page is used after that prerequisite to bypass site isolation.

Published Sep 9, 2026

Updated

Missing authorization in Core 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 HTML page. (Chromium security severity: Low)

Affected Software

1 affected component

Google Google Chrome<153.0.8010.36

Event History

Sep 9, 2026

CVE Published

via MITRE·12:10 AM

Data Sourced

via MITRE·12:10 AM

DescriptionWeakness

Frequently Asked Questions

What access does an attacker need before exploiting this issue?

The attacker must already have compromised the Chrome renderer process. The issue is then exploitable remotely using a crafted HTML page to bypass site isolation.

Which Chrome versions are affected?

Google Chrome versions prior to 153.0.8010.36 are affected.

Are users exposed simply by visiting a malicious page?

The available information does not describe this as a standalone drive-by issue: renderer-process compromise is a stated prerequisite. A crafted HTML page is used after that prerequisite to bypass site isolation.