Skip to content
Noroxi
CVE-2019-16779· NVD / CVE Program· CNA GitHub_M

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

In RubyGem excon before 0.71.0, 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.

MediumCVSS 5.9 · v3.1—No exploit Fix available
Published
Dec 16, 2019
Updated
Jul 28, 2026
EPSS
1.7% · 76th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.7%

CNA vs NVD score

NVD
5.9
CNA · GitHub_M
5.8
0.1 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
excon projectexcon
opensusebackports sle
opensuseleap
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux8.0
  • excon project exconbefore 0.71.0
  • opensuse backports sle15.0
  • opensuse leap15.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • excon excon

    • < 0.71.0 and later · before 0.71.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ruby-exconbefore 0.60.0-20.60.0-2
Debian:8ruby-exconbefore 0.33.0-2+deb8u10.33.0-2+deb8u1
openSUSE:Leap 15.1rubygem-exconbefore 0.59.0-lp151.3.3.10.59.0-lp151.3.3.1
RubyGemsexconbefore 0.71.00.71.0
SUSE:Linux Enterprise Module for Containers 12rubygem-exconbefore 0.52.0-12.3.80.52.0-12.3.8
SUSE:Package Hub 15 SP1rubygem-exconbefore 0.59.0-bp151.4.3.10.59.0-bp151.4.3.1

Other highest-scoring records for the same primary product.

  • CVE-2026-54171Excon: redact additional sensitive/risky headers when following redirects
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-excon0.60.0-2 · Debian:12Package registry (OSV)
opensuse:rubygem-excon0.59.0-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
RubyGems:excon0.71.0Package registry (OSV)
suse:rubygem-excon0.52.0-12.3.8 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records