Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-j5gw-2vrg-8fgx

HIGH

astral-tokio-tar Vulnerable to PAX Header Desynchronization

Also known asCVE-2025-62518RUSTSEC-2025-0110RUSTSEC-2025-0111
Published
Oct 21, 2025
Updated
Feb 4, 2026
Affected
2 pkgs
Patched
1 / 2
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk48th percentile+0.67%
0.00%0.40%0.79%1.19%0.0%0.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
🦀astral-tokio-tar🦀tokio-tar

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Versions 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.

This vulnerability was disclosed to multiple Rust tar parsers, all derived from the original async-tar fork of tar-rs.

Details

Vulnerability Description

The vulnerability stems from inconsistent handling of PAX extended headers versus ustar headers when determining file data boundaries. Specifically:

  1. PAX header correctly specifies the file size (e.g., size=1048576)
  2. ustar header incorrectly specifies zero size (size=000000000000)
  3. tokio-tar advances the stream position based on the ustar size (0 bytes)
  4. Inner content is then interpreted as legitimate outer archive entries

Attack Mechanism

When a TAR file contains:

  • An outer entry with PAX size=N but ustar size=0
  • File data that begins with valid TAR header structures
  • The parser treats inner content as additional outer entries

This creates a header/data desynchronization where the parser's position becomes misaligned with actual file boundaries.

Root Cause

// Vulnerable: Uses ustar size instead of PAX override
let file_size = header.size(); // Returns 0 from ustar field
let next_pos = current_pos + 512 + pad_to_512(file_size); // Advances 0 bytes

// Fixed: Apply PAX overrides before position calculation
let mut file_size = header.size();
if let Some(pax_size) = pending_pax.get("size") {
    file_size = pax_size.parse().unwrap();
}
let next_pos = current_pos + 512 + pad_to_512(file_size); // Correct advance

Impact

The 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.

See 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.

Workarounds

Users are advised to upgrade to version 0.5.6 or newer to address this advisory.

There is no workaround other than upgrading.

Timeline

DateEvent
Aug 21, 2025Vulnerability discovered by Edera Security Team
Aug 21, 2025Initial analysis and PoC confirmed
Aug 22, 2025Maintainers notified (privately)
Aug 25, 2025Private patch and test suite shared
Oct 7, 2025Text freeze for GHSA
Oct 21, 2025Coordinated public disclosure and patched releases

Credits

  • Discovered by: Steven Noonan (Edera) and Alex Zenla (Edera)
  • Coordinated disclosure: Ann Wallace (Edera)

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioastral-tokio-tarall versions0.5.6
🦀crates.iotokio-tarall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for astral-tokio-tar. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update astral-tokio-tar to 0.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j5gw-2vrg-8fgx is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-j5gw-2vrg-8fgx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j5gw-2vrg-8fgx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Versions 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. This vulnerability was disclosed to multiple Rust tar parsers, all derived from the original `async-tar` fork of `tar-rs`
O3 Security · Impact-Aware SCA

Is GHSA-j5gw-2vrg-8fgx in your dependencies?

O3 detects GHSA-j5gw-2vrg-8fgx across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.