dbcve.org
Wget2Application · Gnu

CVE-2025-69195

HIGH · 8.8 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to 2.2.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in GNU Wget2. This vulnerability, a stack-based buffer overflow, occurs in the filename sanitization logic when processing attacker-controlled URL paths, particularly when filename restriction options are active. A remote attacker can exploit this by providing a specially crafted URL, which, upon user interaction with wget2, can lead to memory corruption. This can cause the application to crash and potentially allow for further malicious activities.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack-based buffer overflow vulnerability exists in GNU Wget2's filename sanitization logic. When filename restriction options are enabled, processing attacker-controlled URL paths can overflow a stack-allocated buffer, leading to memory corruption and potential code execution.

MitigationAvoid using wget2 with untrusted URLs until a patch is available. If filename restriction options are not strictly required, consider disabling them as a temporary mitigation. Monitor for wget2 security updates and apply them promptly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wget2Application
Affected:>= 2.1.0, < 2.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify wget2 is installed
    Run 'wget2 --version' or 'which wget2' to confirm wget2 is present on the system
    Affected if wget2 is installed and its version falls within 2.1.0 to 2.2.0 (inclusive)
  2. Determine installed wget2 version
    Execute 'wget2 --version' and parse the version number from the output
    Affected if The reported version is >= 2.1.0 and < 2.2.1
  3. Identify if filename restriction options are enabled
    Check wget2 configuration files (/etc/wgetrc, ~/.wgetrc) and any scripts or cron jobs that invoke wget2 for options that restrict or sanitize filenames (exact option names vary by configuration)
    Affected if Filename restriction options are actively enabled in any wget2 configuration or invocation
  4. Review active wget2 processes
    Run 'ps aux | grep wget2' to inspect any currently running wget2 processes and check their command-line arguments
    Affected if A running wget2 process has filename restriction options enabled in its arguments

A user is affected if wget2 version 2.1.0 through 2.2.0 is installed AND filename restriction options are enabled, as the overflow occurs only when these options are active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.1 or later
Fixed in 2.2.1
Interim mitigation

Avoid using wget2 with untrusted URLs until a patch is available. If filename restriction options are not strictly required, consider disabling them as a temporary mitigation. Monitor for wget2 security updates and apply them promptly.

Recommended fix High confidence

Wget2 2.2.1 or later

  1. Verify current wget2 version by running: wget2 --version
  2. Upgrade wget2 to version 2.2.1 or later using your system's package manager (e.g., apt, yum, dnf, or compile from source)
  3. If using a distribution package manager, run: apt-get update && apt-get install wget2 (Debian/Ubuntu) or dnf update wget2 (Fedora/RHEL 8+)
  4. If compiling from source, download wget2 2.2.1 or later from https://ftp.gnu.org/gnu/wget2/ and follow standard ./configure && make && make install process
  5. Verify the upgrade was successful by running: wget2 --version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wget2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69195 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data