Cross-site information disclosure via navigation isolation bypass
Published Sep 9, 2026 · Updated Sep 10, 2026
Information leak in Google Chrome before 153.0.8010.36 allows remote attackers with a compromised renderer to bypass Site Isolation. The Navigation component permits a crafted HTML page to cross a Site Isolation boundary; Google has not disclosed the responsible function or validation error because bug details remain restricted. Exploitation therefore requires a separate renderer compromise, and the demonstrated consequence is cross-site information exposure rather than code execution or a sandbox escape.
Summary
What happened
Information leak in Google Chrome before 153.0.8010.36 allows remote attackers with a compromised renderer to bypass Site Isolation. The Navigation component permits a crafted HTML page to cross a Site Isolation boundary; Google has not disclosed the responsible function or validation error because bug details remain restricted. Exploitation therefore requires a separate renderer compromise, and the demonstrated consequence is cross-site information exposure rather than code execution or a sandbox escape.
The record
- CVE
- CVE-2026-87541
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=153.0.8010.36 <153.0.8010.36
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo