Is excon 0.105 vulnerable?

RubyGems · 1 release from 0.105.0 to 0.105.0 · latest excon is 1.12.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. excon 0.105.0, the last 0.105 release, is affected by 1 known security advisory (1 medium), including CVE-2026-54171. Upgrade to 1.5.0 or later to fix all of them.

Upgrade with:bundle update --conservative excon # Gemfile: '>= 1.5.0'

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

Advisories affecting excon 0.105.0

  • MediumCVE-2026-54171GHSA-48rx-c7pg-q66r10 Jul 2026

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

    Affected
    <1.5.0
    Fixed in
    1.5.0

Which of your client projects are still on excon 0.105?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact excon version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other excon versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.