CVE-2017-13090

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 37%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
98.3%
KEV
Not listed

Published

October 27, 2017

Last Modified

May 13, 2026

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 / EcosystemFixed in / PatchReleasedSource
ubuntuwget (1.13.4-2ubuntu1.5) @ precise2026-05-22ubuntu
ubuntuwget (1.18-2ubuntu1.1) @ zesty2026-05-22ubuntu
redhatwget-0:1.14-15.el7_4.12017-10-26redhat

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.

  1. 2026-07-06 16:24 UTCEPSS rescore
  2. 2026-07-05 02:27 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-28 14:04 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-27 03:05 UTCEPSS rescore
  8. 2026-06-25 13:47 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-22 22:05 UTCOSV refresh
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-16 17:50 UTCEPSS rescore
  18. 2026-06-15 17:45 UTCEPSS rescore
  19. 2026-06-14 23:14 UTCEPSS rescore
  20. 2026-06-14 23:14 UTCEPSS rescore
  21. 2026-06-13 22:57 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-11 13:57 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-08 14:14 UTCEPSS rescore
Show 34 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-06 13:45 UTCEPSS rescore
  5. 2026-06-05 22:44 UTCEPSS rescore
  6. 2026-06-05 14:27 UTCOSV refresh
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-04 13:10 UTCEPSS rescore
  10. 2026-06-04 13:10 UTCEPSS rescore
  11. 2026-06-02 20:11 UTCEPSS rescore
  12. 2026-06-02 20:11 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 00:14 UTCEPSS rescore
  15. 2026-05-29 13:41 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-27 13:38 UTCEPSS rescore
  20. 2026-05-26 13:42 UTCEPSS rescore
  21. 2026-05-26 13:42 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-22 08:26 UTCEG score recompute
  26. 2026-05-22 08:26 UTCVendor advisory
  27. 2026-05-22 08:26 UTCGHSA enrichment
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-20 22:37 UTCEPSS rescore
  30. 2026-05-20 11:21 UTCEPSS rescore
  31. 2026-05-20 11:21 UTCEPSS rescore
  32. 2026-05-19 19:33 UTCOSV refresh
  33. 2026-05-18 21:30 UTCEPSS rescore
  34. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-13090?
CVE-2017-13090 is a high vulnerability published on October 27, 2017. The retr.c:fdreadbody() 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…
When was CVE-2017-13090 disclosed?
CVE-2017-13090 was first published in the National Vulnerability Database on October 27, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-13090 actively exploited?
CVE-2017-13090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-13090?
CVE-2017-13090 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-13090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-13090, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-13090

Explore →

Is Your Infrastructure Affected by CVE-2017-13090?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.