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.
CVE-2026-54171
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- —
- EPSS
- 36.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 20, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026redact additional sensitive/risky headers when following redirects · Advisory · excon/excon · GitHub
https://github.com/excon/excon/security/advisories/GHSA-48rx-c7pg-q66rexpand redirect header redaction
Fix merged in excon/excon PR #901 on 2026-06-03 — awaiting tagged release
https://github.com/excon/excon/pull/901commit ea89a35308a1 (excon/excon)
Fix landed in excon/excon commit ea89a35308a1 — awaiting tagged release
https://github.com/excon/excon/commit/ea89a35308a12f4b791b6c50f2cbd33f94889fa3Vendor Advisories for CVE-2026-54171(1)
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| excon | 0.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 7× in last 7d / 8× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:42 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-10 21:12 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-54171?
When was CVE-2026-54171 disclosed?
Is CVE-2026-54171 actively exploited?
What is the CVSS score of CVE-2026-54171?
How do I remediate CVE-2026-54171?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54171
Is Your Infrastructure Affected by CVE-2026-54171?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.