Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2019-16779

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Medium5.8EPSS 1.7%
Published
Updated
Reserved
Assigned by
GitHub_M

Description

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.

Scores

CVSS scores of CVE-2019-16779, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1Medium5.8CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
NVDNVD · Analyzed3.1Medium5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
1.7% · top 23% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.8.

Weakness

Affected products

Affected packages

From reviewed advisories of the GitHub Advisory Database.

What to do

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

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-16779 badge
[![CVE-2019-16779](https://trackcve.app/badge/CVE-2019-16779.svg)](https://trackcve.app/cve/CVE-2019-16779)

Record last updated .