MediumGHSA-48rx-c7pg-q66rCVE-2026-54171

Excon does not redact additional sensitive/risky headers when following redirects

Published 10 Jul 2026 · Updated 10 Sept 2026

Is your project on an affected excon?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

exconRubyGems
Affected
<1.5.0
Fixed in
1.5.0
Update to the fixed version for your release line, for example:bundle update --conservative excon # Gemfile: '>= 1.5.0'

Details

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.

Is GHSA-48rx-c7pg-q66r in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected excon, and gives you the command that fixes it.

More advisories for excon

  • MediumCVE-2019-16779In RubyGem excon, interrupted Persistent Connections May Leak Response Data · 16 Dec 2019
excon security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.