The retr.c:fd_read_body() function is called when processing OK responses. When the response is sent chunked in wget before 1.19.2, the chunk parser uses strtol() to read each chunk's length, but doesn't check that the chunk length is a non-negative number. The code then tries to read the chunk in pieces of 8192 bytes by using the MIN() macro, but ends up passing the negative chunk length to retr.c:fd_read(). As fd_read() takes an int argument, the high 32 bits of the chunk length are discarded, leaving fd_read() with a completely attacker controlled length argument. The attacker can corrupt malloc metadata after the allocated buffer.
CVE-2017-13090
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 98.3%
- KEV
- Not listed
Published
October 27, 2017
Last Modified
May 13, 2026
References (16)
- cret@certhttp://git.savannah.gnu.org/cgit/wget.git/commit/?id=ba6b44f6745b14dce414761a8e4b35d31b176bba
- cret@certhttp://www.debian.org/security/2017/dsa-4008
- cret@certhttp://www.securityfocus.com/bid/101590
- cret@certhttp://www.securitytracker.com/id/1039661
- cret@certhttps://access.redhat.com/errata/RHSA-2017:3075
- cret@certhttps://security.gentoo.org/glsa/201711-06
- cret@certhttps://www.synology.com/support/security/Synology_SA_17_62_Wget
- cret@certhttps://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2017/haavoittuvuus-2017-037.html
- af854a3a-2127-422b-91ae-364da2661108http://git.savannah.gnu.org/cgit/wget.git/commit/?id=ba6b44f6745b14dce414761a8e4b35d31b176bba
- af854a3a-2127-422b-91ae-364da2661108http://www.debian.org/security/2017/dsa-4008
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/101590
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1039661
- af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/errata/RHSA-2017:3075
- af854a3a-2127-422b-91ae-364da2661108https://security.gentoo.org/glsa/201711-06
- af854a3a-2127-422b-91ae-364da2661108https://www.synology.com/support/security/Synology_SA_17_62_Wget
Vendor Advisories for CVE-2017-13090(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | wget (1.13.4-2ubuntu1.5) @ precise | 2026-05-22 | ubuntu |
| ubuntu | wget (1.18-2ubuntu1.1) @ zesty | 2026-05-22 | ubuntu |
| redhat | wget-0:1.14-15.el7_4.1 | 2017-10-26 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 4× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-22 22:05 UTCOSV refresh
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-11 13:57 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
Show 34 moreShow fewer
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 14:27 UTCOSV refresh
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-29 13:41 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-26 13:42 UTCEPSS rescore
- 2026-05-26 13:42 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 08:26 UTCEG score recompute
- 2026-05-22 08:26 UTCVendor advisory
- 2026-05-22 08:26 UTCGHSA enrichment
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-19 19:33 UTCOSV refresh
- 2026-05-18 21:30 UTCEPSS rescore
- 2026-05-18 21:30 UTCEPSS rescore
Frequently asked(5)
What is CVE-2017-13090?
When was CVE-2017-13090 disclosed?
Is CVE-2017-13090 actively exploited?
What is the CVSS score of CVE-2017-13090?
How do I remediate CVE-2017-13090?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-13090
Is Your Infrastructure Affected by CVE-2017-13090?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.