{"action":"Upgrade ruby-excon to 0.60.0-2 or later.","affected":[{"fixed":"0.60.0-2","introduced":"0"}],"component":"ruby-excon","cve_ids":[],"ecosystem":"Debian","ecosystem_qualifier":"Debian:13","exploited":false,"fixed_versions":["0.60.0-2"],"id":"tcs_01M5NDZND0T8HTZBYKXW4EQD8X","modified_at":"2026-09-21T07:02:46.013429020Z","published_at":"2019-12-16T20:15:15.540Z","references":["https://osv.dev/vulnerability/DEBIAN-CVE-2019-16779","https://security-tracker.debian.org/tracker/CVE-2019-16779"],"severity":{"label":"medium","score":5.9},"sources":[{"source":"osv","source_id":"DEBIAN-CVE-2019-16779#Debian:13/ruby-excon","url":"https://osv.dev/vulnerability/DEBIAN-CVE-2019-16779"}],"summary":"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 requ"}