Mayuri-Chan pyrofork up to 2.3.68 Telegram Message path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Mayuri-Chan pyrofork up to 2.3.68. The impacted element is an unknown function of the component Telegram Message Handler. Such manipulation leads to path traversal. This vulnerability is traded as CVE-2025-67720. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Mayuri-Chan pyrofork up to 2.3.68 and classified as critical. Affected by this issue is an unknown function of the component Telegram Message Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-67720 since 12/10/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1006.
Upgrading to version 2.3.69 eliminates this vulnerability. Applying the patch 2f2d515575cc9c360bd74340a61a1d2b1e1f1f95 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202512-2247). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 2.3.0
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 2.3.8
- 2.3.9
- 2.3.10
- 2.3.11
- 2.3.12
- 2.3.13
- 2.3.14
- 2.3.15
- 2.3.16
- 2.3.17
- 2.3.18
- 2.3.19
- 2.3.20
- 2.3.21
- 2.3.22
- 2.3.23
- 2.3.24
- 2.3.25
- 2.3.26
- 2.3.27
- 2.3.28
- 2.3.29
- 2.3.30
- 2.3.31
- 2.3.32
- 2.3.33
- 2.3.34
- 2.3.35
- 2.3.36
- 2.3.37
- 2.3.38
- 2.3.39
- 2.3.40
- 2.3.41
- 2.3.42
- 2.3.43
- 2.3.44
- 2.3.45
- 2.3.46
- 2.3.47
- 2.3.48
- 2.3.49
- 2.3.50
- 2.3.51
- 2.3.52
- 2.3.53
- 2.3.54
- 2.3.55
- 2.3.56
- 2.3.57
- 2.3.58
- 2.3.59
- 2.3.60
- 2.3.61
- 2.3.62
- 2.3.63
- 2.3.64
- 2.3.65
- 2.3.66
- 2.3.67
- 2.3.68
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: pyrofork 2.3.69
Patch: 2f2d515575cc9c360bd74340a61a1d2b1e1f1f95
Timeline
12/10/2025 CVE reserved12/11/2025 Advisory disclosed
12/11/2025 VulDB entry created
12/14/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6h2f-wjhf-4wjx
Status: Confirmed
CVE: CVE-2025-67720 (🔒)
GCVE (CVE): GCVE-0-2025-67720
GCVE (VulDB): GCVE-100-335804
CNNVD: CNNVD-202512-2247 - pyrofork 路径遍历漏洞
Entry
Created: 12/11/2025 07:24Updated: 12/14/2025 16:46
Changes: 12/11/2025 07:24 (67), 12/12/2025 16:43 (6), 12/14/2025 01:21 (1), 12/14/2025 16:46 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.