CVE-2026-58469
Heap buffer underread in GNU Wget metalink parsing allows memory corruption.
Is CVE-2026-58469 being exploited?
Not confirmed. CVE-2026-58469 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-58469?
CVE-2026-58469 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58469?
Yes. A fix has been recorded for CVE-2026-58469. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58469 affect?
CVE-2026-58469 affects GNU Wget <= 1.25.0, Systems using Wget to fetch Metalink documents, Linux distributions bundling affected Wget. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58469?
Update Wget to the patched commit/release or apply vendor distro fix
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote memory corruption via crafted Metalink (whitespace-only URL); can crash wget and may enable further exploitation including potential code execution.
Patch when possible
- affected<= 1.25.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.