Memory corruption via inverted filename buffer selection
Published Jan 9, 2026 · Updated Jan 9, 2026
Stack-based buffer overflow in GNU Wget2 2.1.0 through 2.2.0 allows remote attackers to corrupt memory via a crafted URL path. get_local_filename_real() reverses its stack-or-heap buffer choice and passes an undersized fixed 1024-byte stack buffer to wget_restrict_file_name(). The issue requires a user to invoke Wget2 on the URL with filename restrictions active; a crafted path or redirect can crash the process.
Summary
What happened
Stack-based buffer overflow in GNU Wget2 2.1.0 through 2.2.0 allows remote attackers to corrupt memory via a crafted URL path. get_local_filename_real() reverses its stack-or-heap buffer choice and passes an undersized fixed 1024-byte stack buffer to wget_restrict_file_name(). The issue requires a user to invoke Wget2 on the URL with filename restrictions active; a crafted path or redirect can crash the process.
The record
- CVE
- CVE-2025-69195
- Published
- Jan 9, 2026
- Updated
- Jan 9, 2026
- Vendor
- The GnuPG Project
- Product
- Wget2
- Classifications
- CWE-121, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2026CVE publishedPublication date reported by the CVE source.
- Jan 9, 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=2.1.0 <=2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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