CVE-2025-62518: Astral tokio tar Astral-tokio-tar Vulnerable To PAX Header Vulnerability
HIGHCVE-2025-62518 is a HIGH (CVSS 8.1) astral-tokio-tar vulnerable to pax header vulnerability (CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')) affecting Astral tokio tar libraries in the crates.io ecosystem. The issue involves astral-tokio-tar vulnerable to pax header desynchronization. Remediation is available by upgrading affected packages to version 0.5.6.
CVE-2025-62518 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).
How to Fix CVE-2025-62518
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.
Upgrade astral-tokio-tar to 0.5.6
Upgrade tokio-tar to Latest secure release
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-62518, 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.6), 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-843: Access of Resource Using Incompatible Type ('Type Confusion'), where the product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. 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
CVE-2025-62518 Affected Astral tokio tar Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
astral-tokio-tar
|
crates.io |
< 0.5.6
|
0.5.6
|
|
tokio-tar
|
crates.io |
≤ 0.3.1
|
|
References
Frequently Asked Questions
What is CVE-2025-62518?
Which Astral tokio tar versions are affected?
What version fixes CVE-2025-62518?
Is astral-tokio-tar affected?
Is tokio-tar affected?
What is the CVSS score of CVE-2025-62518?
What CWE is associated with CVE-2025-62518?
How can I check crates.io dependencies for CVE-2025-62518?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j5gw-2vrg-8fgx",
"modified" : "2026-01-16T22:12:12Z",
"published" : "2025-10-21T15:42:51Z",
"aliases" : [ "CVE-2025-62518" ],
"summary" : "astral-tokio-tar Vulnerable to PAX Header Desynchronization",
"details" : "## Summary\n\nVersions of `astral-tokio-tar` prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers.\n\nThis vulnerability was disclosed to multiple Rust tar parsers, all derived from the original `async-tar` fork of `tar-rs`.\n\n## Details\n\n### Vulnerability Description\n\nThe vulnerability stems from inconsistent handling of PAX extended headers versus ustar headers when determining file data boundaries. Specifically:\n\n1. **PAX header** correctly specifies the file size (e.g., `size=1048576`)\n2. **ustar header** incorrectly specifies zero size (`size=000000000000`)\n3. **tokio-tar** advances the stream position based on the ustar size (0 bytes)\n4. **Inner content** is then interpreted as legitimate outer archive entries\n\n### Attack Mechanism\n\nWhen a TAR file contains:\n\n- An outer entry with PAX `size=N` but ustar `size=0`\n- File data that begins with valid TAR header structures\n- The parser treats inner content as additional outer entries\n\nThis creates a **header/data desynchronization** where the parser's position becomes misaligned with actual file boundaries.\n\n### Root Cause\n\n```rust\n// Vulnerable: Uses ustar size instead of PAX override\nlet file_size = header.size(); // Returns 0 from ustar field\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Advances 0 bytes\n\n// Fixed: Apply PAX overrides before position calculation\nlet mut file_size = header.size();\nif let Some(pax_size) = pending_pax.get(\"size\") {\n file_size = pax_size.parse().unwrap();\n}\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Correct advance\n\n```\n\n## Impact\n\nThe impact of this vulnerability depends on where `astral-tokio-tar` is used, and whether it is used to extract untrusted tar archives. If used to extract untrusted inputs, it may result in unexpected attacker-controlled access to the filesystem, in turn potential resulting in arbitrary code execution or credential exfiltration.\n\nSee [**GHSA-w476-p2h3-79g9**](https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9) 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\n## Workarounds\n\nUsers are advised to upgrade to version 0.5.6 or newer to address this advisory.\n\nThere is no workaround other than upgrading.\n\n## Timeline\n\n| Date | Event |\n| --- | --- |\n| Aug 21, 2025 | Vulnerability discovered by Edera Security Team |\n| Aug 21, 2025 | Initial analysis and PoC confirmed |\n| Aug 22, 2025 | Maintainers notified (privately) |\n| Aug 25, 2025 | Private patch and test suite shared |\n| Oct 7, 2025 | Text freeze for GHSA |\n| Oct 21, 2025 | Coordinated public disclosure and patched releases |\n\n## Credits\n\n- **Discovered by:** Steven Noonan (Edera) and Alex Zenla (Edera)\n- **Coordinated disclosure:** Ann Wallace (Edera)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "astral-tokio-tar"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.5.6"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.5.5"
}
}, {
"package" : {
"ecosystem" : "crates.io",
"name" : "tokio-tar"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.3.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-j5gw-2vrg-8fgx"
}, {
"type" : "WEB",
"url" : "https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9"
}, {
"type" : "WEB",
"url" : "https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318"
}, {
"type" : "WEB",
"url" : "https://edera.dev/stories/tarmageddon"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/astral-sh/tokio-tar"
}, {
"type" : "WEB",
"url" : "https://github.com/edera-dev/cve-tarmageddon"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2025-0110.html"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2025-0111.html"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-843" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-10-21T15:42:51Z",
"nvd_published_at" : "2025-10-21T17:15:40Z"
}
}