Cross-origin data disclosure via Link-header referrer leakage
Published May 14, 2025 · Updated Jun 5, 2025
Policy enforcement failure in Google Chrome before 136.0.7103.113 allows remote attackers to leak cross-origin data via crafted HTML. The Loader resolves Link headers on subresource responses and sends follow-on requests with the full document URL in the Referer header, bypassing cross-origin referrer restrictions. A user must load the crafted page, after which secrets embedded in the initiating URL's path or query can reach an attacker-controlled origin.
Summary
What happened
Policy enforcement failure in Google Chrome before 136.0.7103.113 allows remote attackers to leak cross-origin data via crafted HTML. The Loader resolves Link headers on subresource responses and sends follow-on requests with the full document URL in the Referer header, bypassing cross-origin referrer restrictions. A user must load the crafted page, after which secrets embedded in the initiating URL's path or query can reach an attacker-controlled origin.
The record
- CVE
- CVE-2025-4664
- Published
- May 14, 2025
- Updated
- Jun 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2025CVE publishedPublication date reported by the CVE source.
- Jun 5, 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=136.0.7103.113 <136.0.7103.113
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.
Public exploit references
- Link-header referrer-leak demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Google report of in-the-wild vulnerability knowledgereported exploitation
- CISA Known Exploited Vulnerabilities Catalog listingknown exploited catalog
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