GHSA-xx64-wwv2-hcqq: astral-tokio-tar `unpack_in` Can Chmod Arbitrary Directories Vulnerability

LOW
CWE-61
Published
Advisory Summary

GHSA-xx64-wwv2-hcqq is a LOW `unpack_in` can chmod arbitrary directories vulnerability (CWE-61: UNIX Symbolic Link (Symlink) Following) affecting astral-tokio-tar libraries in the crates.io ecosystem. The issue involves `unpack_in` can chmod arbitrary directories by following symlinks. Remediation is available by upgrading affected packages to version 0.6.1.

GHSA-xx64-wwv2-hcqq at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xx64-wwv2-hcqq
Severity LOW
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 GHSA-xx64-wwv2-hcqq

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.6.1
Upgrade astral-tokio-tar to 0.6.1
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 GHSA-xx64-wwv2-hcqq, 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.6.1), 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.6.0 and earlier of astral-tokio-tar, the `unpack_in` API could inadvertently modify the permissions of external (i.e. non-archive) directories outside of the archive. An attacker could use this to contrite a tar archive that maliciously changes directory permissions outside of its intended hierarchy. This flaw only affects directories; individual file permissions cannot be modified via it. See GHSA-j4xf-2g29-59ph for the equivalent flaw in the `tar` crate. ### Patches Versions 0.6.1 and newer of astral-tokio-tar use `fs::symlink_metdata` rather than `fs::metadata`, avoiding the traversal. ### Workarounds Users are advised to upgrade to version 0.6.1 or newer to address this advisory. Users should experience no breaking changes as a result of the patch above. ### Resources - GHSA-j4xf-2g29-59ph for the original `tar` vulnerability ### Attribution - Reporter: Adam Harvey (@lawngnome)

GHSA-xx64-wwv2-hcqq Affected astral-tokio-tar Versions

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

References

Frequently Asked Questions

What is GHSA-xx64-wwv2-hcqq?
GHSA-xx64-wwv2-hcqq is a security vulnerability in astral-tokio-tar involving `unpack_in` can chmod arbitrary directories by following symlinks under CWE-61: UNIX Symbolic Link (Symlink) Following.
Which astral-tokio-tar versions are affected?
Affected versions include releases prior to 0.6.1 across affected packages: astral-tokio-tar.
What version fixes GHSA-xx64-wwv2-hcqq?
Upgrading to 0.6.1 (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.6.1. Upgrade your dependency to 0.6.1 or later.
What CWE is associated with GHSA-xx64-wwv2-hcqq?
GHSA-xx64-wwv2-hcqq 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 GHSA-xx64-wwv2-hcqq?
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-xx64-wwv2-hcqq",
  "modified" : "2026-05-06T17:26:39Z",
  "published" : "2026-05-06T17:26:38Z",
  "aliases" : [ ],
  "summary" : "astral-tokio-tar: `unpack_in` can chmod arbitrary directories by following symlinks",
  "details" : "### Impact\n\nIn versions 0.6.0 and earlier of astral-tokio-tar, the `unpack_in` API could inadvertently modify the permissions of external (i.e. non-archive) directories outside of the archive. An attacker could use this to contrite a tar archive that maliciously changes directory permissions outside of its intended hierarchy. This flaw only affects directories; individual file permissions cannot be modified via it.\n\nSee GHSA-j4xf-2g29-59ph for the equivalent flaw in the `tar` crate.\n\n### Patches\n\nVersions 0.6.1 and newer of astral-tokio-tar use `fs::symlink_metdata` rather than `fs::metadata`, avoiding the traversal. \n\n### Workarounds\n\nUsers are advised to upgrade to version 0.6.1 or newer to address this advisory.\n\nUsers should experience no breaking changes as a result of the patch above.\n\n### Resources\n\n- GHSA-j4xf-2g29-59ph for the original `tar` vulnerability\n\n### Attribution\n\n- Reporter: Adam Harvey (@lawngnome)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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.6.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.6.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-xx64-wwv2-hcqq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-xx64-wwv2-hcqq"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/astral-sh/tokio-tar"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0113.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-61" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-06T17:26:38Z",
    "nvd_published_at" : null
  }
}