CVE-2025-67720
Pyrofork is a modern, asynchronous MTProto API framework. Versions …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/Mayuri-Chan/pyrofork/security/advisories/GHSA-6h2f-wjhf-4wjx
- github.com/Mayuri-Chan/pyrofork/commit/2f2d515575cc9c360bd74340a61a1d2b1e1f1f95
- nvd.nist.gov/vuln/detail/CVE-2025-67720
- github.com/advisories/GHSA-6h2f-wjhf-4wjx
- nvd.nist.gov/vuln/detail/CVE-2025-67720
- cve.org/CVERecord?id=CVE-2025-67720
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.