CVE-2026-67354
Guzzle redirect handling can leak URL fragments via Referer header.
Is CVE-2026-67354 being exploited?
Not confirmed. CVE-2026-67354 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-67354?
CVE-2026-67354 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67354?
Yes. A fix has been recorded for CVE-2026-67354. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67354 affect?
CVE-2026-67354 affects guzzlehttp/guzzle < 7.15.1, PHP applications using allow_redirects.referer, Services following same-scheme redirects. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67354?
Upgrade to guzzle 7.15.1 or disable allow_redirects.referer; strip fragments server-side.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker controlling a redirect can read URI fragments (tokens, one‑time secrets, state) from Referer, disclosing sensitive client data.
Patch when possible
- affected< 7.15.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.