CVE-2026-58470

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH 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(high)
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.20.3-1ubuntu2.1+esm2) @ focal2026-07-28ubuntu

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.

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 22× in last 7d / 58× 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-28 15:37 UTCEPSS rescore
  2. 2026-07-28 09:06 UTCEG score recompute
  3. 2026-07-28 09:06 UTCVendor advisory
  4. 2026-07-28 09:06 UTCGHSA enrichment
  5. 2026-07-27 14:14 UTCEPSS rescore
  6. 2026-07-27 10:50 UTCEG score recompute
  7. 2026-07-27 10:50 UTCVendor advisory
  8. 2026-07-27 10:50 UTCGHSA enrichment
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-26 12:36 UTCEG score recompute
  12. 2026-07-26 12:36 UTCVendor advisory
  13. 2026-07-26 12:36 UTCGHSA enrichment
  14. 2026-07-25 14:18 UTCEPSS rescore
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:21 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-21 15:25 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 33 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 14:31 UTCEPSS rescore
  3. 2026-07-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-17 02:42 UTCVendor advisory
  6. 2026-07-17 02:42 UTCGHSA enrichment
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 04:29 UTCVendor advisory
  9. 2026-07-16 04:29 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 06:17 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 08:03 UTCGHSA enrichment
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 09:40 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-12 11:27 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 13:14 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-10 15:01 UTCGHSA enrichment
  26. 2026-07-09 19:10 UTCEPSS rescore
  27. 2026-07-09 19:10 UTCEPSS rescore
  28. 2026-07-09 16:49 UTCGHSA enrichment
  29. 2026-07-08 18:35 UTCGHSA enrichment
  30. 2026-07-08 15:16 UTCEPSS rescore
  31. 2026-07-08 15:16 UTCEPSS rescore
  32. 2026-07-07 20:22 UTCEG score recompute
  33. 2026-07-07 20:21 UTCMITRE cvelistV5first tracked

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.9% 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

Explore the affected products and dependency analysis for 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.