CVE-2025-62518 | astral-tokio-tar Vulnerable to PAX Header Desynchronization

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.

Published: 2025-10-21 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-62518 is rated Low Risk (33.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-62518

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-22 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-62518

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]

Weakness enumeration for CVE-2025-62518

GitHub Security Advisory for CVE-2025-62518

GHSA-j5gw-2vrg-8fgx · Severity: high · Ecosystem: rust — astral-tokio-tar Vulnerable to PAX Header Desynchronization

OS Trackers for CVE-2025-62518

vendor priority summary link
debian not yet assigned CVE-2025-62518 not yet assigned priority: Debian including 1 source packages (rust-astral-tokio-tar), 3 status rows across 3 suites (forky, sid, trixie): resolved 2, open 1. https://security-tracker.debian.org/tracker/CVE-2025-62518
redhat high — https://access.redhat.com/security/cve/CVE-2025-62518
suse medium CVE-2025-62518 severity moderate: SUSE including 10 source package names (python311-uv-0.9.5-1.1, python312-uv-0.9.5-1.1, …), 13 product×package rows across 4 product lines (SUSE Linux Enterprise Server 16.0, SUSE Linux Enterprise Server for SAP applications 16.0, openSUSE Leap 16.0, openSUSE Tumbleweed): Fixed 12, First Fixed 1. https://www.suse.com/security/cve/CVE-2025-62518/
ubuntu medium CVE-2025-62518 medium priority: Ubuntu including 1 source packages (rust-astral-tokio-tar), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): DNE 2, ignored 1, needs-triage 1, released 1. https://ubuntu.com/security/CVE-2025-62518

Affected software / configurations for CVE-2025-62518

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-62518

cvelogic Threat Intelligence