excon vulnerabilities

EXtended http(s) CONnections

Registry
RubyGems
Latest
1.12.0
License
MIT

2 known advisories

The latest version, 1.12.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:bundle update --conservative excon # Gemfile: '>= 1.12.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

Security advisories for excon

  • 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
  • MediumCVE-2019-16779GHSA-q58g-455p-8vw916 Dec 2019

    In RubyGem excon, interrupted Persistent Connections May Leak Response Data

    Affected
    <0.71.0
    Fixed in
    0.71.0

Is your excon version vulnerable?

Which of your client projects still run an old excon?

NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other RubyGems packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.