In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.017, the 76th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 15:16 UTC First seen by agentprime
2. 31 Oct 2026, 15:16 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-q58g-455p-8vw9
• OSV: GHSA-q58g-455p-8vw9
• github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9
• nvd.nist.gov/vuln/detail/CVE-2019-16779
• github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29
• github.com/excon/excon
• github.com/rubysec/ruby-advisory-db/blob/master/gems/excon/CVE-2019-16779.yml
• lists.debian.org/debian-lts-announce/2020/01/msg00015.html
• lists.opensuse.org/opensuse-security-announce/2020-01/msg00021.html
• lists.opensuse.org/opensuse-security-announce/2020-01/msg00062.html

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.