Описание
Excon does not redact additional sensitive/risky headers when following redirects
Impact
The redirect follower middleware previously failed to strip a number of headers that are known to be sensitive and did not provide a way to provide a custom list of headers to strip.
What kind of vulnerability is it? Who is impacted? This could cause inadvertent leakage of sensitive data for users of the RedirectFollower middleware in cases where the initial request includes header information that is not intended for the new target.
Patches
Patch exists and is released in v1.5.0
Workarounds
Users can backport the fix to a custom redirect follower middleware.
Ссылки
- https://github.com/excon/excon/security/advisories/GHSA-48rx-c7pg-q66r
- https://nvd.nist.gov/vuln/detail/CVE-2026-54171
- https://github.com/excon/excon/pull/901
- https://github.com/excon/excon/commit/ea89a35308a12f4b791b6c50f2cbd33f94889fa3
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/excon/CVE-2026-54171.yml
- https://www.cve.org/CVERecord?id=CVE-2026-54171
Пакеты
excon
< 1.5.0
1.5.0
Связанные уязвимости
(Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon ...)
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.
Excon: redact additional sensitive/risky headers when following redirects
Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon ...