CVE-2017-13089

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 80% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 80%
CISA-KEV: Not listedEPSS PROB: 80%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The http.c:skip_short_body() function is called in some circumstances, such as when processing redirects. 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 skip the chunk in pieces of 512 bytes by using the MIN() macro, but ends up passing the negative chunk length to connect.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.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
77
EG Risk 77/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation80% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
80%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 27, 2017

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Aug 14, 2026
Patch available. Sources: redhat.
generic

Fix stack overflow in HTTP protocol handling (CVE-2017-13089) - wget.git - GNU Wget

http://git.savannah.gnu.org/cgit/wget.git/commit/?id=d892291fb8ace4c3b734ea5125770989c215df3f
generic

Traficom – liikenteen ja viestinnän palvelut sinulle | Traficom

https://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2017/haavoittuvuus-2017-037.html
generic

Synology_SA_17_62_Wget | Synology Inc.

https://www.synology.com/support/security/Synology_SA_17_62_Wget
generic

GNU Wget: Multiple vulnerabilities (GLSA 201711-06) — Gentoo security

https://security.gentoo.org/glsa/201711-06
generic

GitHub - r1b/CVE-2017-13089: PoC for wget v1.19.1 · GitHub

https://github.com/r1b/CVE-2017-13089
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:3075
generic

[SECURITY] [DSA 4008-1] wget security update

http://www.debian.org/security/2017/dsa-4008

Vendor Advisories for CVE-2017-13089(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuwget (1.13.4-2ubuntu1.5) @ precise2026-05-22ubuntu
ubuntuwget (1.19.1-3ubuntu1.1) @ artful2026-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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.18-r2: fixed in 1.18-r2
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.18-r3: fixed in 1.18-r3
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.19.2-1: fixed in 1.19.2-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.19.2-1: fixed in 1.19.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.19.2-1: fixed in 1.19.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wget—
  • every version up to 1.19.2-1: fixed in 1.19.2-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
wget1.13.4-3, 1.13.4-3+deb7u1, 1.13.4-3+deb7u2, 1.13.4-3+deb7u3, 1.13.4-3+deb7u4
  • every version up to 1.13.4-3+deb7u5: fixed in 1.13.4-3+deb7u5
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
wget1.16-1, 1.16-1+deb8u1, 1.16-1+deb8u2
  • every version up to 1.16-1+deb8u4: fixed in 1.16-1+deb8u4
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
wget1.18-5
  • every version up to 1.18-5+deb9u1: fixed in 1.18-5+deb9u1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 / 14× 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-10-07 23:41 UTCEPSS rescore
  2. 2026-10-07 21:54 UTCOSV refresh
  3. 2026-10-06 15:11 UTCEPSS rescore
  4. 2026-10-03 14:21 UTCEPSS rescore
  5. 2026-09-30 09:25 UTCEG score recompute
  6. 2026-09-28 13:45 UTCEPSS rescore
  7. 2026-09-26 15:53 UTCEPSS rescore
  8. 2026-09-24 13:59 UTCEPSS rescore
  9. 2026-09-18 19:22 UTCEPSS rescore
  10. 2026-09-18 03:50 UTCOSV refresh
  11. 2026-09-17 19:22 UTCEPSS rescore
  12. 2026-09-15 03:05 UTCEPSS rescore
  13. 2026-09-12 14:55 UTCEPSS rescore
  14. 2026-09-10 09:26 UTCEPSS rescore
  15. 2026-09-04 05:01 UTCEPSS rescore
  16. 2026-08-30 19:13 UTCEPSS rescore
  17. 2026-08-30 04:48 UTCOSV refresh
  18. 2026-08-28 21:36 UTCEPSS rescore
  19. 2026-08-27 14:20 UTCEPSS rescore
  20. 2026-08-26 14:41 UTCEPSS rescore
  21. 2026-08-24 14:10 UTCEPSS rescore
  22. 2026-08-20 22:50 UTCEPSS rescore
  23. 2026-08-19 16:59 UTCEPSS rescore
  24. 2026-08-16 02:10 UTCEPSS rescore
  25. 2026-08-15 01:26 UTCEPSS rescore
Show 62 more
  1. 2026-08-13 18:21 UTCOSV refresh
  2. 2026-07-30 16:24 UTCEPSS rescore
  3. 2026-07-28 22:51 UTCOSV refresh
  4. 2026-07-26 14:51 UTCEPSS rescore
  5. 2026-07-25 14:13 UTCEPSS rescore
  6. 2026-07-23 01:26 UTCEG score recompute▲ 0.20
  7. 2026-07-22 22:05 UTCEG score recompute
  8. 2026-07-22 14:04 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-13 22:26 UTCEPSS rescore
  16. 2026-07-11 15:41 UTCOSV refresh
  17. 2026-07-11 08:24 UTCEPSS rescore
  18. 2026-07-08 15:10 UTCEPSS rescore
  19. 2026-07-04 06:28 UTCEPSS rescore
  20. 2026-07-01 15:02 UTCEPSS rescore
  21. 2026-07-01 15:02 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-22 22:05 UTCOSV refresh
  26. 2026-06-21 14:54 UTCEPSS rescore
  27. 2026-06-21 14:54 UTCEPSS rescore
  28. 2026-06-21 01:57 UTCEPSS rescore
  29. 2026-06-21 01:57 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 17:45 UTCEPSS rescore
  32. 2026-06-13 22:57 UTCEPSS rescore
  33. 2026-06-12 23:09 UTCEPSS rescore
  34. 2026-06-11 13:57 UTCEPSS rescore
  35. 2026-06-10 22:15 UTCEPSS rescore
  36. 2026-06-08 14:14 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-05 22:44 UTCEPSS rescore
  40. 2026-06-05 14:27 UTCOSV refresh
  41. 2026-06-05 06:08 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-04 13:10 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-02 20:11 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-01 13:49 UTCEPSS rescore
  48. 2026-06-01 13:49 UTCEPSS rescore
  49. 2026-05-31 00:14 UTCEPSS rescore
  50. 2026-05-29 13:41 UTCEPSS rescore
  51. 2026-05-28 13:42 UTCEPSS rescore
  52. 2026-05-28 13:42 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore
  54. 2026-05-26 07:17 UTCEPSS rescore
  55. 2026-05-22 21:15 UTCEPSS rescore
  56. 2026-05-22 21:15 UTCEPSS rescore
  57. 2026-05-22 21:15 UTCEPSS rescore
  58. 2026-05-22 08:26 UTCEG score recompute
  59. 2026-05-22 08:26 UTCVendor advisory
  60. 2026-05-22 08:26 UTCGHSA enrichment
  61. 2026-05-18 21:30 UTCEPSS rescore
  62. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmzeyong/CVE-2017-13089
    First seen Nov 15, 2017

    CVE-2017-13089

    Open source ↗
  • GitHub PoCr1b/CVE-2017-13089
    First seen Oct 27, 2017

    PoC for wget v1.19.1

    Open source ↗

Frequently asked(5)

What is CVE-2017-13089?
CVE-2017-13089 is a critical vulnerability published on October 27, 2017. The http.c:skipshortbody() function is called in some circumstances, such as when processing redirects. 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…
When was CVE-2017-13089 disclosed?
CVE-2017-13089 was first published on October 27, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-13089 actively exploited?
CVE-2017-13089 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 80% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-13089?
CVE-2017-13089 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2017-13089?
A fix for CVE-2017-13089 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-13089 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-13089

Explore →

Is Your Infrastructure Affected by CVE-2017-13089?

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