cve.bz

CVE-2026-58470 gnu wget: Year 2038 problem, Y2K38, Y2038, Epochalypse

6.9 mediumEPSS 0.2%Fix available

Medium (6.9) in gnu wget. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-58470 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-58470?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-58470?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-58470 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-58470

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-58470](https://cve.bz/cve/badge/CVE-2026-58470.svg)](https://cve.bz/cve/CVE-2026-58470)

HTML:

<a href="https://cve.bz/cve/CVE-2026-58470"><img src="https://cve.bz/cve/badge/CVE-2026-58470.svg" alt="CVE-2026-58470"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gnuwget wgetthrough 1.25.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14wgetno fix listedDEBIAN-CVE-2026-58470
Ubuntu22.04:LTSwget1.21.2-2ubuntu1.3UBUNTU-CVE-2026-58470 USN-8543-1
Ubuntu24.04:LTSwget1.21.4-1ubuntu4.3UBUNTU-CVE-2026-58470 USN-8543-1
Ubuntu25.10wgetno fix listedUBUNTU-CVE-2026-58470
Ubuntu26.04:LTSwget1.25.0-2ubuntu4.2UBUNTU-CVE-2026-58470 USN-8543-1
UbuntuPro:14.04:LTSwget1.15-1ubuntu1.14.04.5+esm2UBUNTU-CVE-2026-58470 USN-8543-1
UbuntuPro:16.04:LTSwget1.17.1-1ubuntu1.5+esm3UBUNTU-CVE-2026-58470 USN-8543-1
UbuntuPro:18.04:LTSwget1.19.4-1ubuntu2.2+esm3UBUNTU-CVE-2026-58470 USN-8543-1
UbuntuPro:20.04:LTSwget1.20.3-1ubuntu2.1+esm2UBUNTU-CVE-2026-58470 USN-8543-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 6 morewget1.20.3-150000.3.34.1SUSE-SU-2026:3206-1
SUSELinux Enterprise Module for Basesystem 15 SP7wget1.24.5-150700.3.3.1SUSE-SU-2026:3148-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0wget1.25.0-160000.3.1SUSE-SU-2026:23326-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5wget1.14-21.28.1SUSE-SU-2026:3205-1
SUSELinux Micro 6.0wget1.24.5-3.1SUSE-SU-2026:23053-1
SUSELinux Micro 6.1wget1.24.5-slfo.1.1_4.1SUSE-SU-2026:23163-1
SUSELinux Micro 6.2wget1.25.0-160000.3.1SUSE-SU-2026:23297-1
openSUSELeap 16.0wget1.25.0-160000.3.1openSUSE-SU-2026:21665-1
openSUSETumbleweedwget1.25.0-3.1openSUSE-SU-2026:11252-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate: GNU Wget is vulnerable to a client-side integer overflow in its Content-Range header processing. If a client connects to an attacker-controlled server, the server can return anomalous headers that cause undefined behavior and stream desynchronization. This results in local data integrity issues or a denial of service, though the impact is strictly limited to the Wget process itself.

Red Hat's mitigation

To mitigate this issue, users should avoid using `wget` to download content from untrusted or unverified sources. When `wget` is used in automated scripts or environments, ensure that the target servers are trusted to prevent exposure to malicious `Content-Range` headers. Restricting network access for `wget` to only trusted hosts can also reduce the attack surface.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10wgetFix deferred
Red Hat Enterprise Linux 6wgetOut of support scope
Red Hat Enterprise Linux 7wgetOut of support scope
Red Hat Enterprise Linux 8wgetFix deferred
Red Hat Enterprise Linux 9wgetFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-58470.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON