# CVE-2025-69194: Wget2: arbitrary file write via metalink path traversal in gnu wget2

> Attackers can write files to arbitrary locations via Metalink path traversal in GNU Wget2, potentially leading to data loss or system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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-73901, DEBIAN-CVE-2025-69194, GHSA-82jv-f4jx-8r27, MGASA-2026-0002, UBUNTU-CVE-2025-69194

## What is CVE-2025-69194?

CVE-2025-69194 is a high-severity path traversal 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 security issue was discovered in GNU Wget2 when handling Metalink documents. The application fails to properly validate file paths provided in Metalink <file name> elements. An attacker can abuse this behavior to write files to unintended locations on the system. This can lead to data loss or potentially allow further compromise of the user’s environment.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Gnu Wget2.

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

Upgrade to a fixed version.

## Is CVE-2025-69194 being exploited?

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

Public exploit code:

- PoC for CVE-2025-69194, a Path Traversal vulnerability in GNU Wget2 <= 2.2.0. This vulnerability allows attackers to achieve arbitrary file write or overwrite on the victim's filesystem by providing a malicious Metalink file with manipulated file name attributes. (github_poc): https://github.com/secdongle/POC_CVE-2025-69194

## Other vulnerabilities in gnu:wget2

- [CVE-2025-69195](https://insights.sbomify.com/CVE-2025-69195/): Wget2: gnu wget2: memory corruption and crash via filename sanitization logic with attacker-controlled urls (high 7.6)
- [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-69194 and fix it if it is affected.

What it is: CVE-2025-69194 is a high-severity path traversal 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-69194 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-69194/ (Markdown: https://insights.sbomify.com/CVE-2025-69194/index.md)
```

## Sources

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

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