CVE-2025-59825
BaseFortify
Publication date: 2025-09-23
Last updated on: 2025-09-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| astral | tokio-tar | 0.5.4 |
| uv | uv | 0.6.6 |
| astral | tokio-tar | 0.5.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| CWE-61 | The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the astral-tokio-tar library (version 0.5.3 and earlier) used for reading and writing tar archives asynchronously in Rust. It allows tar archives to extract files outside of their intended destination directory when using the Entry::unpack_in_raw API. Additionally, the security control Entry::allow_external_symlinks, which is meant to prevent extraction outside the target directory, can be bypassed using a pair of symlinks that individually point inside the destination but together point outside. This can lead to arbitrary file writes and potentially allow an attacker to execute code.
How can this vulnerability impact me? :
If you use astral-tokio-tar version 0.5.3 or earlier to extract tar archives, an attacker could craft a malicious tar archive that exploits this vulnerability to write files outside the intended directory. This could lead to unauthorized file overwrites and potentially allow the attacker to execute arbitrary code on your system, compromising its security.
What immediate steps should I take to mitigate this vulnerability?
The only mitigation is to upgrade astral-tokio-tar to version 0.5.4 or later, as there is no workaround other than upgrading.