# CVE-2026-58470: GNU Wget 1.25.0 Integer Overflow via Content-Range Header Parsing

> Attackers can cause denial of service in GNU Wget by sending malicious Content-Range headers that trigger an integer overflow.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** CLSA-2026-1784310537, DEBIAN-CVE-2026-58470, ECHO-18f1-7a81-eb45, GHSA-5f52-px6m-c5hw, JLSEC-2026-1159, ROOT-OS-DEBIAN-11-CVE-2026-58470, ROOT-OS-DEBIAN-13-CVE-2026-58470, UBUNTU-CVE-2026-58470

## What is CVE-2026-58470?

CVE-2026-58470 is a medium-severity vulnerability in gnuwget wget, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-58470?

It affects 1 product.


Products: Gnu Wget.

## How do I fix CVE-2026-58470?

Apply the vendor's patch.

## Is CVE-2026-58470 being exploited?

There is no known exploitation of CVE-2026-58470 in the wild and no public exploit code.

## Other vulnerabilities in gnuwget wget

- [CVE-2019-5953](https://insights.sbomify.com/CVE-2019-5953/): Memory corruption in GNU Wget (critical 9.8)
- [CVE-2014-4877](https://insights.sbomify.com/CVE-2014-4877/): Path traversal in n/a (critical 9.3)
- [CVE-2024-38428](https://insights.sbomify.com/CVE-2024-38428/): Other in n/a (critical 9.1)
- [CVE-2026-58469](https://insights.sbomify.com/CVE-2026-58469/): GNU Wget 1.25.0 Heap Buffer Underread via Metalink URL Parsing (high 8.7)
- [CVE-2016-7098](https://insights.sbomify.com/CVE-2016-7098/): Race condition in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58470 and fix it if it is affected.

What it is: CVE-2026-58470 is a medium-severity vulnerability in gnuwget wget, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58470 in the wild and no public exploit code.

Affected product: gnuwget wget. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58470/ (Markdown: https://insights.sbomify.com/CVE-2026-58470/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58470
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58470
- OSV: https://osv.dev/vulnerability/CVE-2026-58470

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58470/
Summaries are generated and may contain mistakes; the official description above is the record.