CVE-2026-87570: High severity Google Google Chrome vulnerability
Chromium CVE-2026-87570: Incorrect authorization in SiteIsolation
Other sources
Incorrect authorization in SiteIsolation in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass site isolation via a crafted file. (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
Google Chrome/Chromium (SiteIsolation)to a version that resolves this vulnerability.Fixed in 153.0.8010.36 - Compensating control
If feasible, harden/monitor renderer process compromise and reduce the ability for an attacker to social-engineer bypass of Site Isolation (e.g., tighten user interaction requirements and security monitoring around file handling and renderer activity).
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 and then use social engineering to get the victim to interact with a crafted file. The issue is not described as exploitable solely by visiting a website.
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.
What is the practical impact of successful exploitation?
A successful attacker can bypass Chrome site isolation after meeting the renderer-compromise and social-engineering prerequisites. Site isolation is intended to separate content from different sites, so the bypass weakens that boundary.