Site isolation bypass via navigation side channel
Published Dec 3, 2025 · Updated Dec 3, 2025
Side-channel information leakage in Google Chrome before 139.0.7258.66 allows remote attackers to bypass site isolation via crafted HTML. Google identifies Navigation and Loading as the locus but keeps the linked bug details restricted, so the precise leaking operation is undisclosed. Exploitation requires a user to open attacker-controlled HTML; the demonstrated consequence is cross-site information exposure, with no integrity or availability impact reported.
Summary
What happened
Side-channel information leakage in Google Chrome before 139.0.7258.66 allows remote attackers to bypass site isolation via crafted HTML. Google identifies Navigation and Loading as the locus but keeps the linked bug details restricted, so the precise leaking operation is undisclosed. Exploitation requires a user to open attacker-controlled HTML; the demonstrated consequence is cross-site information exposure, with no integrity or availability impact reported.
The record
- CVE
- CVE-2025-13992
- Published
- Dec 3, 2025
- Updated
- Dec 3, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-1300, CAPEC-189, CAPEC-699, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record 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=139.0.7258.66 <139.0.7258.66
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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