Skip to main content
Public proof of conceptFix available

CVE-2025-62518

A public proof of concept exists; no exploitation attested.

  • Published2025-10-21
  • WeaknessCWE-843

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-10-2117:15CVE publishedNVD

Versions per branch

OSV
tokio-tar
BranchAffectedFixed in
0.0+≥ 0.0.0-0no fix published
0.3≤ 0.3.1no fix published
astral-tokio-tar
BranchAffectedFixed in
0.x≥ 0.0.0-0, < 0.5.60.5.6
0.5< 0.5.60.5.6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • astral-sh tokio-tar
    Affected
    • = < 0.5.6no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-10-21

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • pixiWolfiall versions · fixed in 0.57.0-r1and 1 other package
  • pixiChainguardall versions · fixed in 0.57.0-r1and 1 other package
  • py3.10-uv-buildMinimOSall versions · fixed in 0.9.5-r0and 12 other packages
  • python-uvSUSE:Linux Enterprise Server for SAP applications 16.0all versions · fixed in 0.7.18-160000.3.1
  • python-uvSUSE:Linux Enterprise Server 16.0all versions · fixed in 0.7.18-160000.3.1
  • python-uvopenSUSE:Tumbleweedall versions · fixed in 0.9.5-1.1
  • python-uvopenSUSE:Leap 16.0all versions · fixed in 0.7.18-160000.3.1
  • rust-astral-tokio-tarUbuntu:26.04:LTSall versions · no fixed version listed

6 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-62518 Red Hat Product Security5 known affected

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

    openshift-sandboxed-containers/osc-podvm-builder-rhel9 as a component of Confidential Compute Attestation · openshift-sandboxed-containers/osc-podvm-payload-rhel9 as a component of Confidential Compute Attestation · openshift-sandboxed-containers/osc-rhel9-operator as a component of Confidential Compute Attestation · +2 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2025-62518 · 5 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  2. No fix available, says the vendor Red Hat Product Security CVE-2025-62518 · 3 productsAffected
  3. No fix planned, says the vendor Red Hat Product Security CVE-2025-62518 · 2 productsWill not fix

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Published
2025-10-21
Last Modified
2026-10-08
NVD status
Deferred
GitHub Advisory
GHSA-j5gw-2vrg-8fgx

Frequently asked questions

What is CVE-2025-62518?

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.

Is CVE-2025-62518 actively exploited?

A proof-of-concept exploit exists for CVE-2025-62518, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2025-62518?

CVE-2025-62518 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.

Running tokio-tar? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record