Memory corruption via filename conversion buffer miscalculation
Published Jul 7, 2026 · Updated Jul 7, 2026
Heap buffer overflow in GNU Wget 1.25.0 and earlier allows remote attackers to corrupt memory via a server-supplied filename. The convert_fname() loop in src/url.c reallocates its iconv output buffer after E2BIG but calculates remaining capacity from the wrong position, allowing subsequent conversion output to exceed the heap allocation. Triggering requires Wget to retrieve a response whose filename needs character-set conversion; the grounded consequence is memory corruption, with no demonstrated public exploit.
Summary
What happened
Heap buffer overflow in GNU Wget 1.25.0 and earlier allows remote attackers to corrupt memory via a server-supplied filename. The convert_fname() loop in src/url.c reallocates its iconv output buffer after E2BIG but calculates remaining capacity from the wrong position, allowing subsequent conversion output to exceed the heap allocation. Triggering requires Wget to retrieve a response whose filename needs character-set conversion; the grounded consequence is memory corruption, with no demonstrated public exploit.
The record
- CVE
- CVE-2026-58471
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- The GnuPG Project
- Product
- GNU Wget
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.25.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo