CVE-2026-54171 json
Excon: redact additional sensitive/risky headers when following redirects
published 2026-07-10 4 mo ago modified 2026-09-10 1 mo ago also EUVD-2026-45312 , GHSA-48rx-c7pg-q66r
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rubygems excon 1.5.0
- excon_project excon 1.5.0
- ruby-excon Debian 14 1.5.0-1
debian advisories DEBIAN-CVE-2026-54171
- github.com/excon/excon@ea89a35 commit
- github.com/excon/excon#901 pull request
- github.com/excon/excon/security/advisories/GHSA-48rx-c7pg-q66r advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-54171 updated cvss 6.5
excon: Excon: Information disclosure via unstripped sensitive headers during redirects
-
Red Hat 3scale API Management Platform 2 3scale-amp2/zync-rhel9 Red Hat Satellite 6 rubygem-exconaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | excon | <1.5.0 |
1.5.0 |
Affected products
- excon excon
Classification
References
-
github.com
/excon/excon/pull/901
web, issue-tracking, patch
-
github.com
/excon/excon/commit/ea89a35308a12f4b791b6c50f2cbd33f94889fa3
web, patch
-
github.com
/excon/excon/security/advisories/GHSA-48rx-c7pg-q66r
web, patch, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-54171
advisory
-
github.com
/excon/excon
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/excon/CVE-2026-54171.yml
web
-
cve.org
/CVERecord?id=CVE-2026-54171
web
Sources
- CVE List CVE-2026-54171
- GitHub Advisory GHSA-48rx-c7pg-q66r
- NVD CVE-2026-54171
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.