Skip to content
Fencer Vulns
high 8.1

CVE-2025-62518 json

astral-tokio-tar Vulnerable to PAX Header Desynchronization

published 2025-10-21 12 mo ago modified 2026-10-12 27 d ago also EUVD-2025-35176 , GHSA-j5gw-2vrg-8fgx , RUSTSEC-2025-0110 , RUSTSEC-2025-0111

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

astral-tokio-tar is a tar archive reading/writing library for async Rust. 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 issue has been patched in version 0.5.6. There are no workarounds.

Patch / fix

  • crates.io astral-tokio-tar 0.5.6
  • astral-sh astral-tokio-tar 0.5.6
  • astral-sh tokio-tar 0.5.6
  • astral astral-tokio-tar 0.5.6
  • astral tokio-tar 0.5.6
  • rust-astral-tokio-tar Debian 14 0.5.6-1

debian advisories DEBIAN-CVE-2025-62518

  • python-uv SLES for SAP applications 16.0, SLES 16.0 0.7.18-160000.3.1

suse advisories SUSE-SU-2026:20077-1

  • zed openSUSE Tumbleweed 1.24.2-1.1
  • python-uv openSUSE Leap 16.0 0.7.18-160000.3.1
  • python-uv openSUSE Tumbleweed 0.9.5-1.1

opensuse advisories openSUSE-SU-2026:12355-1openSUSE-SU-2026:20026-1openSUSE-SU-2025:15658-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-62518 updated cvss 8.1

astral-tokio-tar: astral-tokio-tar Vulnerable to PAX Header Desynchronization

  • Red Hat Confidential Compute Attestation openshift-sandboxed-containers/osc-rhel9-operator, openshift-sandboxed-containers/osc-podvm-builder-rhel9, openshift-sandboxed-containers/osc-podvm-payload-rhel9
    affected: workaround, no fix available
  • Red Hat OpenShift Container Platform 4 kata-containers
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Confidential Compute Attestation openshift-sandboxed-containers/osc-monitor-rhel9, openshift-sandboxed-containers/osc-operator-bundle Red Hat Enterprise Linux 9 trustee-guest-components
    not affected: component not present
  • Red Hat Enterprise Linux 10 trustee-guest-components
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
crates.io astral-tokio-tar
<0.5.6
>=0.0.0-0, <0.5.6
0.5.6
crates.io tokio-tar
<=0.3.1
>=0.0.0-0
 no fix listed

Affected products

  • astral-sh tokio-tar

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.