cve.bz

CVE-2025-62518 astral-sh tokio-tar: Type Confusion

8.1 highEPSS 0.7%Fix available

High (8.1) in astral-sh tokio-tar. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in astral-tokio-tar 0.5.6.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-10-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-62518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62518?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62518?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62518 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
astral-sh tokio-tar< 0.5.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j5gw-2vrg-8fgxcrates.ioastral-tokio-tar<0.5.60.5.6
GHSA-j5gw-2vrg-8fgxcrates.iotokio-tar<=0.3.1no fix published
RUSTSEC-2025-0110crates.ioastral-tokio-tar>=0.0.0-0 <0.5.60.5.6
RUSTSEC-2025-0111crates.iotokio-tar>=0.0.0-0no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13rust-astral-tokio-tarno fix listedDEBIAN-CVE-2025-62518
Debian14rust-astral-tokio-tar0.5.6-1DEBIAN-CVE-2025-62518
Ubuntu25.10, 26.04:LTSrust-astral-tokio-tarno fix listedUBUNTU-CVE-2025-62518
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0python-uv0.7.18-160000.3.1SUSE-SU-2026:20077-1
openSUSELeap 16.0python-uv0.7.18-160000.3.1openSUSE-SU-2026:20026-1
openSUSETumbleweedpython-uv0.9.5-1.1openSUSE-SU-2025:15658-1
openSUSETumbleweedzed1.24.2-1.1openSUSE-SU-2026:12355-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

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

ProductPackageStateAdvisory
Confidential Compute Attestationopenshift-sandboxed-containers/osc-monitor-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-operator-bundleNot affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-builder-rhel9Affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-payload-rhel9Affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-rhel9-operatorAffected
Red Hat Enterprise Linux 10trustee-guest-componentsNot affected
Red Hat Enterprise Linux 9trustee-guest-componentsNot affected
Red Hat OpenShift Container Platform 4kata-containersWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-62518.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON