CVE-2025-59825: Astral tokio tar Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-3wgq-wrwc-vqmv
CWE-61 CWE-22
Published
Advisory Summary

CVE-2025-59825 is a MODERATE path traversal vulnerability (CWE-61: UNIX Symbolic Link (Symlink) Following) affecting Astral tokio tar libraries in the crates.io ecosystem. The issue involves astral-tokio-tar has a path traversal in tar extraction. Remediation is available by upgrading affected packages to version 0.5.4.

CVE-2025-59825 at a Glance

CVE Identifier CVE-2025-59825
GHSA Identifier GHSA-3wgq-wrwc-vqmv
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-61: UNIX Symbolic Link (Symlink) Following
Affected Product Astral tokio tar
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2025-59825

To remediate this vulnerability, upgrade all affected Astral tokio tar dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

astral-tokio-tar fixed: 0.5.4
Upgrade astral-tokio-tar to 0.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for astral-tokio-tar

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-59825, inspect your project dependencies for Astral tokio tar:

inspect dependencies for astral-tokio-tar

Analyze the terminal output to locate any version of Astral tokio tar in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-61: UNIX Symbolic Link (Symlink) Following, where 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. In Astral tokio tar, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact In versions 0.5.3 and earlier of astral-tokio-tar, tar archives may extract outside of their intended destination directory when using the `Entry::unpack_in_raw` API. Additionally, the `Entry::allow_external_symlinks` control (which defaults to `true`) could be bypassed via a pair of symlinks that individually point within the destination but combine to point outside of it. These behaviors could be used individually or combined to bypass the intended security control of limiting extraction to the given directory. This in turn would allow an attacker with a malicious tar archive to perform an arbitrary file write and potentially pivot into code execution (e.g. by overwriting a file that the user or system then executes or uses to execute code). The impact of this vulnerability for downstream API users of this crate is **high**, per above. However, for this crate's main downstream user (uv), the impact of this vulnerability is **low** due to its overlap with equivalent user capabilities in source distributions. See GHSA-7j9j-68r2-f35q for additional details. ### Patches Versions 0.5.4 and newer of astral-tokio-tar address the vulnerability above. Users should upgrade to 0.5.4 or newer. ### Workarounds Users are advised to upgrade to version 0.5.4 or newer to address this advisory. There is no workaround other than upgrading. ### References * See GHSA-7j9j-68r2-f35q for how this vulnerability affects uv, astral-tokio-tar's primary downstream user. Observe that **unlike** this advisory, uv's advisory is considered **low severity** due to overlap with intentional existing capabilities in source distributions. * This vulnerability is similar to (but not related in code) to CVE-2025-4138 and CVE-2025-4517, which concern Python's tarfile module.

CVE-2025-59825 Affected Astral tokio tar Versions

1 component(s)
Fixed Versions:
0.5.4
Product / Package Ecosystem Affected Versions Fixed Version
astral-tokio-tar
crates.io
< 0.5.4
0.5.4

References

Frequently Asked Questions

What is CVE-2025-59825?
CVE-2025-59825 is a security vulnerability in Astral tokio tar involving astral-tokio-tar has a path traversal in tar extraction under CWE-61: UNIX Symbolic Link (Symlink) Following.
Which Astral tokio tar versions are affected?
Affected versions include releases prior to 0.5.4 across affected packages: astral-tokio-tar.
What version fixes CVE-2025-59825?
Upgrading to 0.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is astral-tokio-tar affected?
Yes, astral-tokio-tar is affected in releases prior to 0.5.4. Upgrade your dependency to 0.5.4 or later.
What CWE is associated with CVE-2025-59825?
CVE-2025-59825 is classified under CWE-61: UNIX Symbolic Link (Symlink) Following (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.).
How can I check crates.io dependencies for CVE-2025-59825?
Run the dependency tree command: 'inspect dependencies for astral-tokio-tar'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3wgq-wrwc-vqmv",
  "modified" : "2025-11-18T16:40:30Z",
  "published" : "2025-09-23T17:45:07Z",
  "aliases" : [ "CVE-2025-59825" ],
  "summary" : "astral-tokio-tar has a path traversal in tar extraction",
  "details" : "### Impact\n\nIn versions 0.5.3 and earlier of astral-tokio-tar, tar archives may extract outside of their intended destination directory when using the `Entry::unpack_in_raw` API. Additionally, the `Entry::allow_external_symlinks` control (which defaults to `true`) could be bypassed via a pair of symlinks that individually point within the destination but combine to point outside of it.\n\nThese behaviors could be used individually or combined to bypass the intended security control of limiting extraction to the given directory. This in turn would allow an attacker with a malicious tar archive to perform an arbitrary file write and potentially pivot into code execution (e.g. by overwriting a file that the user or system then executes or uses to execute code). \n\nThe impact of this vulnerability for downstream API users of this crate is **high**, per above. However, for this crate's main downstream user (uv), the impact of this vulnerability is **low** due to its overlap with equivalent user capabilities in source distributions. See GHSA-7j9j-68r2-f35q for additional details.\n\n### Patches\n\nVersions 0.5.4 and newer of astral-tokio-tar address the vulnerability above. Users should upgrade to 0.5.4 or newer.\n\n### Workarounds\n\nUsers are advised to upgrade to version 0.5.4 or newer to address this advisory.\n\nThere is no workaround other than upgrading.\n\n### References\n\n* See GHSA-7j9j-68r2-f35q for how this vulnerability affects uv, astral-tokio-tar's primary downstream user. Observe that **unlike** this advisory, uv's advisory is considered **low severity** due to overlap with intentional existing capabilities in source distributions.\n* This vulnerability is similar to (but not related in code) to CVE-2025-4138 and CVE-2025-4517, which concern Python's tarfile module.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "astral-tokio-tar"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.5.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.5.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-3wgq-wrwc-vqmv"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/google/security-research/security/advisories/GHSA-9p78-p5g6-gcj8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/issues/12163"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/tokio-tar/commit/036fdecc85c52458ace92dc9e02e9cef90684e75"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/astral-sh/tokio-tar"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-61" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-23T17:45:07Z",
    "nvd_published_at" : "2025-09-23T20:15:33Z"
  }
}