CVE-2026-58470

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-07. the CNA's CVSS baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

GNU Wget through 1.25.0, fixed in commit 43d3ba9, contains an integer overflow vulnerability in the parse_content_range() function within src/http.c that allows server-controlled values to cause signed integer arithmetic to overflow. Attackers can supply malicious Content-Range header values to trigger undefined behavior and download desynchronization in the affected client.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

GNU Wget 1.25.0 Integer Overflow via Content-Range Header Parsing | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gnu-wget-integer-overflow-via-content-range-header-parsing
generic

* src/http.c (parse_content_range): Fix integer overflow (43d3ba93) · Commits · Wget / wget · GitLab

https://gitlab.com/gnuwget/wget/-/commit/43d3ba9336bc94937e6fae2365c6ffd30c34ffcf

Vendor Advisories for CVE-2026-58470(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuwget (1.21.4-1ubuntu4.3) @ noble2026-09-18ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wget1.21-1 ... 1.25.0-3 (12 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wget1.21.3-1 ... 1.25.0-3 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wget1.25.0-2, 1.25.0-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wget1.25.0-2, 1.25.0-3——

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 56× 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.

Showing the most recent 100 of 211 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:50 UTCEG score recompute
  4. 2026-09-18 05:50 UTCVendor advisory
  5. 2026-09-18 05:50 UTCGHSA enrichment
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:11 UTCEPSS rescore
  10. 2026-09-14 06:42 UTCEG score recompute
  11. 2026-09-14 06:42 UTCVendor advisory
  12. 2026-09-14 06:42 UTCGHSA enrichment
  13. 2026-09-13 16:47 UTCEPSS rescore
  14. 2026-09-13 08:29 UTCEG score recompute
  15. 2026-09-13 08:29 UTCVendor advisory
  16. 2026-09-13 08:29 UTCGHSA enrichment
  17. 2026-09-12 03:43 UTCEG score recompute
  18. 2026-09-12 03:43 UTCVendor advisory
  19. 2026-09-12 03:43 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 22:53 UTCEG score recompute
Show 75 more
  1. 2026-09-05 22:53 UTCVendor advisory
  2. 2026-09-05 22:53 UTCGHSA enrichment
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 07:42 UTCEG score recompute
  9. 2026-08-30 07:42 UTCVendor advisory
  10. 2026-08-30 07:42 UTCGHSA enrichment
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-27 21:55 UTCEG score recompute
  14. 2026-08-27 21:55 UTCVendor advisory
  15. 2026-08-27 21:55 UTCGHSA enrichment
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-26 12:59 UTCEG score recompute
  19. 2026-08-26 12:59 UTCVendor advisory
  20. 2026-08-26 12:59 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 20:38 UTCEG score recompute
  23. 2026-08-24 20:38 UTCVendor advisory
  24. 2026-08-24 20:38 UTCGHSA enrichment
  25. 2026-08-23 19:05 UTCEG score recompute
  26. 2026-08-23 19:05 UTCVendor advisory
  27. 2026-08-23 19:05 UTCGHSA enrichment
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 20:52 UTCEG score recompute
  30. 2026-08-22 20:52 UTCVendor advisory
  31. 2026-08-22 20:52 UTCGHSA enrichment
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 22:39 UTCVendor advisory
  34. 2026-08-21 22:39 UTCGHSA enrichment
  35. 2026-08-21 00:25 UTCEG score recompute
  36. 2026-08-21 00:25 UTCVendor advisory
  37. 2026-08-21 00:24 UTCGHSA enrichment
  38. 2026-08-20 22:55 UTCEPSS rescore
  39. 2026-08-20 02:12 UTCEG score recompute
  40. 2026-08-20 02:12 UTCVendor advisory
  41. 2026-08-20 02:12 UTCGHSA enrichment
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-18 20:47 UTCEG score recompute
  44. 2026-08-18 20:47 UTCVendor advisory
  45. 2026-08-18 20:47 UTCGHSA enrichment
  46. 2026-08-18 13:48 UTCEPSS rescore
  47. 2026-08-17 22:33 UTCEG score recompute
  48. 2026-08-17 22:33 UTCVendor advisory
  49. 2026-08-17 22:33 UTCGHSA enrichment
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-16 20:02 UTCEG score recompute
  52. 2026-08-16 20:02 UTCVendor advisory
  53. 2026-08-16 20:02 UTCGHSA enrichment
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 02:14 UTCEPSS rescore
  56. 2026-08-15 21:49 UTCEG score recompute
  57. 2026-08-15 21:49 UTCVendor advisory
  58. 2026-08-15 21:49 UTCGHSA enrichment
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 23:36 UTCVendor advisory
  61. 2026-08-14 23:36 UTCGHSA enrichment
  62. 2026-08-14 01:24 UTCEG score recompute
  63. 2026-08-14 01:24 UTCVendor advisory
  64. 2026-08-14 01:24 UTCGHSA enrichment
  65. 2026-08-13 22:00 UTCEPSS rescore
  66. 2026-08-13 03:12 UTCEG score recompute
  67. 2026-08-13 03:12 UTCVendor advisory
  68. 2026-08-13 03:12 UTCGHSA enrichment
  69. 2026-08-12 13:51 UTCEPSS rescore
  70. 2026-08-12 04:59 UTCEG score recompute
  71. 2026-08-12 04:59 UTCVendor advisory
  72. 2026-08-12 04:59 UTCGHSA enrichment
  73. 2026-08-11 06:46 UTCEG score recompute
  74. 2026-08-11 06:46 UTCVendor advisory
  75. 2026-08-11 06:46 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58470?
CVE-2026-58470 is a medium vulnerability published on July 7, 2026. GNU Wget through 1.25.0, fixed in commit 43d3ba9, contains an integer overflow vulnerability in the parsecontentrange() function within src/http.c that allows server-controlled values to cause signed integer arithmetic to overflow. Attackers can supply malicious Content-Range header values to…
When was CVE-2026-58470 disclosed?
CVE-2026-58470 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58470 actively exploited?
CVE-2026-58470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.7% of all scored CVEs.
What is the CVSS score of CVE-2026-58470?
CVE-2026-58470 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-58470?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58470, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58470

Explore →

Is Your Infrastructure Affected by CVE-2026-58470?

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

Start Free Scan →Browse All CVEs