CVE-2026-67354: guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer
guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allowredirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
guzzlehttp/guzzleto a version that resolves this vulnerability.Fixed in 7.15.1 - Configuration
Ensure the optional allow_redirects.referer setting is disabled (referer setting is disabled by default) so the middleware does not copy the URI fragment into the Referer header on redirects.
RedirectMiddleware (allow_redirects.referer) allow_redirects.referer = false
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67354?
CVE-2026-67354 has a medium severity rating of 5.9.
How do I fix CVE-2026-67354?
To fix CVE-2026-67354, update guzzlehttp/guzzle to version 7.15.1 or later.
What type of vulnerability is CVE-2026-67354?
CVE-2026-67354 is an information disclosure vulnerability.
Which versions of guzzlehttp/guzzle are affected by CVE-2026-67354?
Versions of guzzlehttp/guzzle before 7.15.1 are affected by CVE-2026-67354.
What does the URI Fragment Disclosure in CVE-2026-67354 impact?
CVE-2026-67354 impacts the Referer header by potentially exposing sensitive URI fragment information.