CVE-2026-87433: Race Condition
Chromium CVE-2026-87433: Race condition in FileAPI
Other sources
Race condition in FileAPI 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: Medium)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 153.0.4234.32 - Upgrade
Upgrade
Chromium (Google Chrome / Edge Chromium-based)to a version that resolves this vulnerability.Fixed in 153.0.8010.36 - Compensating control
If applicable, strengthen isolation/containment for renderer compromises to reduce the impact of bypassing site isolation (e.g., ensure site isolation is enabled and harden renderer-to-site isolation boundaries).
Event History
Frequently Asked Questions
What must an attacker achieve before this issue can be exploited?
The attacker must first compromise the Chrome renderer process. Exploitation then uses a crafted HTML page to bypass site isolation.
Which Chrome versions are affected?
Google Chrome versions prior to 153.0.8010.36 are affected.
What security boundary can exploitation bypass?
Successful exploitation can bypass Chrome site isolation after the renderer process has been compromised.