CVE-2026-87487: Google Chrome vulnerability

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

The attacker must first compromise the Chrome renderer process and then leverage social engineering to get the target to interact with a crafted HTML page. The issue is therefore not described as a standalone, direct remote-code-execution path.

Q: What is the potential impact after successful exploitation?

A successful exploit could allow arbitrary code execution outside Chrome's sandbox. This could turn a renderer compromise into a sandbox escape.

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 described.

Published Sep 9, 2026

Updated

Missing authorization in FileSystem in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially execute arbitrary code outside the sandbox 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 and then leverage social engineering to get the target to interact with a crafted HTML page. The issue is therefore not described as a standalone, direct remote-code-execution path.

What is the potential impact after successful exploitation?

A successful exploit could allow arbitrary code execution outside Chrome's sandbox. This could turn a renderer compromise into a sandbox escape.

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 described.