Sensitive-fragment disclosure via generated Referer header
Published Aug 1, 2026 · Updated Aug 1, 2026
Information disclosure in Guzzle RedirectMiddleware before 7.15.1 allows remote attackers to read URI fragments via redirected Referer headers. RedirectMiddleware retains a referring URI's fragment and copies it into the generated Referer header when following a same-scheme redirect. Exploitation requires the disabled-by-default referer setting, a sensitive fragment, and a redirect to a less-trusted destination; the destination can read the fragment in request data or logs.
Summary
What happened
Information disclosure in Guzzle RedirectMiddleware before 7.15.1 allows remote attackers to read URI fragments via redirected Referer headers. RedirectMiddleware retains a referring URI's fragment and copies it into the generated Referer header when following a same-scheme redirect. Exploitation requires the disabled-by-default referer setting, a sensitive fragment, and a redirect to a less-trusted destination; the destination can read the fragment in request data or logs.
The record
- CVE
- CVE-2026-67354
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Guzzle
- Product
- Guzzle
- Classifications
- CWE-212, CWE-201
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=0 <7.15.1
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