# CVE-2025-69195: Wget2: gnu wget2: memory corruption and crash via filename sanitization logic with attacker-controlled urls

> A stack-based buffer overflow in GNU Wget2 allows remote attackers to cause crashes or execute code via crafted URLs when filename restrictions are enabled.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** AZL-73904, DEBIAN-CVE-2025-69195, GHSA-q2gj-jpwc-8f46, UBUNTU-CVE-2025-69195

## What is CVE-2025-69195?

CVE-2025-69195 is a high-severity memory corruption vulnerability in gnu:wget2, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-69195?

It affects 1 product.


Products: Gnu Wget2.

## How do I fix CVE-2025-69195?

Apply the vendor's patch.

## Is CVE-2025-69195 being exploited?

There is no known exploitation of CVE-2025-69195 in the wild and no public exploit code.

## Other vulnerabilities in gnu:wget2

- [CVE-2025-69194](https://insights.sbomify.com/CVE-2025-69194/): Wget2: arbitrary file write via metalink path traversal in gnu wget2 (high 8.8)
- [CVE-2026-1858](https://insights.sbomify.com/CVE-2026-1858/): wget2 Improper Certificate Validation (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69195 and fix it if it is affected.

What it is: CVE-2025-69195 is a high-severity memory corruption vulnerability in gnu:wget2, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-69195 in the wild and no public exploit code.

Affected product: gnu:wget2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-69195/ (Markdown: https://insights.sbomify.com/CVE-2025-69195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-69195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-69195
- OSV: https://osv.dev/vulnerability/CVE-2025-69195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-69195/
Summaries are generated and may contain mistakes; the official description above is the record.