CVE-2026-54171

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial request includes header information that is not intended for the new target. This issue is fixed in version 1.5.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

redact additional sensitive/risky headers when following redirects · Advisory · excon/excon · GitHub

https://github.com/excon/excon/security/advisories/GHSA-48rx-c7pg-q66r
github_pr

expand redirect header redaction

Fix merged in excon/excon PR #901 on 2026-06-03 — awaiting tagged release

https://github.com/excon/excon/pull/901
github_commit

commit ea89a35308a1 (excon/excon)

Fix landed in excon/excon commit ea89a35308a1 — awaiting tagged release

https://github.com/excon/excon/commit/ea89a35308a12f4b791b6c50f2cbd33f94889fa3

Vendor Advisories for CVE-2026-54171(2)

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

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
excon0.0.1 ... 1.4.2 (278 versions)1.5.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 17× 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-07-27 05:57 UTCEG score recompute
  2. 2026-07-27 05:57 UTCVendor advisory
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 05:06 UTCEG score recompute
  5. 2026-07-26 05:06 UTCVendor advisory
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:19 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 03:42 UTCEG score recompute
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-10 21:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54171?
CVE-2026-54171 is a medium vulnerability published on July 10, 2026. Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial…
When was CVE-2026-54171 disclosed?
CVE-2026-54171 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54171 actively exploited?
CVE-2026-54171 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 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54171?
CVE-2026-54171 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54171, 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-54171

Explore →

Is Your Infrastructure Affected by CVE-2026-54171?

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

Start Free Scan →Browse All CVEs