MediumGHSA-q58g-455p-8vw9CVE-2019-16779

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Published 16 Dec 2019 · 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
<0.71.0
Fixed in
0.71.0
Update to the fixed version for your release line, for example:bundle update --conservative excon # Gemfile: '>= 0.71.0'

Details

Impact

There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.

Patches

The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).

Workarounds

Users can workaround the problem by disabling persistent connections, though this may cause performance implications.

References

See the patch for further details.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in excon/issues
  • Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com)

Is GHSA-q58g-455p-8vw9 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-2026-54171Excon does not redact additional sensitive/risky headers when following redirects · 10 Jul 2026
excon security overview

References

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