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.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).

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
36%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 29, 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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-excon0.112.0-1 ... 1.6.0-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-excon0.112.0-1 ... 1.6.0-1 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-excon0.112.0-4 ... 1.6.0-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-excon0.112.0-4 ... 1.4.2-1 (7 versions)1.5.0-1—
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 14× in last 7d / 73× 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-30 06:12 UTCEG score recompute
  2. 2026-08-30 06:12 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 21:40 UTCEG score recompute
  6. 2026-08-27 21:40 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 12:53 UTCEG score recompute
  10. 2026-08-26 12:53 UTCVendor advisory
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 10:03 UTCEG score recompute
  13. 2026-08-25 10:03 UTCVendor advisory
  14. 2026-08-24 09:25 UTCVendor advisory
  15. 2026-08-23 07:10 UTCEG score recompute
  16. 2026-08-23 07:10 UTCVendor advisory
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 06:32 UTCEG score recompute
  19. 2026-08-22 06:32 UTCVendor advisory
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 05:54 UTCEG score recompute
  22. 2026-08-21 05:54 UTCVendor advisory
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 05:17 UTCEG score recompute
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 04:39 UTCEG score recompute
  2. 2026-08-19 04:39 UTCVendor advisory
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-18 03:44 UTCEG score recompute
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 02:51 UTCEG score recompute
  7. 2026-08-17 02:51 UTCVendor advisory
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCVendor advisory
  11. 2026-08-15 01:35 UTCEG score recompute
  12. 2026-08-15 01:35 UTCVendor advisory
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 00:58 UTCEG score recompute
  15. 2026-08-14 00:58 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 00:20 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 23:43 UTCEG score recompute
  20. 2026-08-11 23:43 UTCVendor advisory
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-09 22:27 UTCEG score recompute
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-08 21:50 UTCEG score recompute
  25. 2026-08-08 21:50 UTCVendor advisory
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-07 21:12 UTCEG score recompute
  28. 2026-08-06 20:35 UTCEG score recompute
  29. 2026-08-06 20:35 UTCVendor advisory
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-05 19:57 UTCEG score recompute
  32. 2026-08-05 19:57 UTCVendor advisory
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-04 19:20 UTCEG score recompute
  35. 2026-08-04 19:20 UTCVendor advisory
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:39 UTCEPSS rescore
  38. 2026-08-03 18:42 UTCEG score recompute
  39. 2026-08-03 18:42 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 18:05 UTCEG score recompute
  42. 2026-08-02 18:05 UTCVendor advisory
  43. 2026-08-02 02:27 UTCEPSS rescore
  44. 2026-08-01 17:27 UTCEG score recompute
  45. 2026-08-01 17:27 UTCVendor advisory
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-31 16:49 UTCEG score recompute
  48. 2026-07-31 16:49 UTCVendor advisory
  49. 2026-07-30 16:28 UTCEPSS rescore
  50. 2026-07-30 16:09 UTCEG score recompute
  51. 2026-07-30 16:09 UTCVendor advisory
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-29 15:24 UTCVendor advisory
  54. 2026-07-29 07:32 UTCEG score recompute
  55. 2026-07-29 07:32 UTCVendor advisory
  56. 2026-07-28 15:37 UTCEPSS rescore
  57. 2026-07-28 06:37 UTCEG score recompute
  58. 2026-07-28 06:37 UTCVendor advisory
  59. 2026-07-27 05:57 UTCEG score recompute
  60. 2026-07-27 05:57 UTCVendor advisory
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 05:06 UTCEG score recompute
  63. 2026-07-26 05:06 UTCVendor advisory
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-24 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 03:19 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescore
  69. 2026-07-21 15:25 UTCEPSS rescore
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 03:42 UTCEG score recompute
  74. 2026-07-19 02:29 UTCEPSS rescore
  75. 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 29, 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 64.5% 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