CVE-2026-67354

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
Patch available. Sources: github.
generic

guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer | Advisories | VulnCheck

https://www.vulncheck.com/advisories/guzzlehttp-guzzle-before-uri-fragment-disclosure-via-referer
github Patch Available

URI fragments disclosed in redirect Referer headers in guzzlehttp/guzzle · Advisory · guzzle/guzzle · GitHub

https://github.com/guzzle/guzzle/security/advisories/GHSA-h95v-h523-3mw8

Vendor Advisories for CVE-2026-67354(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
guzzle7.11.0-1 ... 8.0.1-1 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
guzzle7.11.0-1 ... 8.0.1-1 (12 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
guzzle7.11.0-1 ... 7.9.2-0.1 (10 versions)7.15.1-1—
Packagist(1)
PackageVulnerable rangeFixed inDependents
guzzlehttp/guzzle4.0.0 ... v3.8.1 (174 versions)7.15.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 10:12 UTCEG score recompute
  3. 2026-08-24 11:42 UTCEG score recompute
  4. 2026-08-23 13:12 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 14:32 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 16:02 UTCEG score recompute
  9. 2026-08-20 22:56 UTCEPSS rescore
  10. 2026-08-19 19:02 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 19:32 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 21:01 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 22:31 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-15 01:31 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 03:01 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 04:32 UTCEG score recompute
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 06:02 UTCEG score recompute
  25. 2026-08-11 07:33 UTCEG score recompute
Show 24 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-10 09:02 UTCEG score recompute
  3. 2026-08-09 13:47 UTCEPSS rescore
  4. 2026-08-09 10:33 UTCEG score recompute
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-08 12:03 UTCEG score recompute
  7. 2026-08-06 15:04 UTCEG score recompute
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 18:02 UTCEG score recompute
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 10:39 UTCEPSS rescore
  14. 2026-08-03 19:18 UTCEG score recompute
  15. 2026-08-03 19:18 UTCGHSA enrichment
  16. 2026-08-03 19:05 UTCEG score recompute
  17. 2026-08-03 19:05 UTCGHSA enrichment
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-03 10:24 UTCGHSA enrichment
  20. 2026-08-02 11:48 UTCEG score recompute
  21. 2026-08-02 11:48 UTCGHSA enrichment
  22. 2026-08-01 13:18 UTCEG score recompute
  23. 2026-08-01 12:43 UTCEG score recompute
  24. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67354?
CVE-2026-67354 is a medium vulnerability published on August 1, 2026. 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 was CVE-2026-67354 disclosed?
CVE-2026-67354 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67354 actively exploited?
CVE-2026-67354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-67354?
CVE-2026-67354 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-67354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67354, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67354

Explore →

Is Your Infrastructure Affected by CVE-2026-67354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs