Vulnerability advisory
CVE-2026-67354
guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer
Also known as GHSA-h95v-h523-3mw8
- CVSS 4.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/guzzle/guzzle ↗ | |
| All commits before 61443dfb33c62f308ee8add20f45b4d6e4bf8d2f | 61443dfb33c62f308ee8add20f45b4d6e4bf8d2f |
Also listed as affected (144)
| |
Description
guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.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.
References
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67354.json ↗
- Advisorygithub.com/guzzle/guzzle/security/advisories/GHSA-h95v-h523-3mw8 ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-67354 ↗
- Advisorywww.vulncheck.com/advisories/guzzlehttp-guzzle-before-uri-fragment-disclosure-via-referer ↗