UBUNTU-CVE-2025-62518 (CVE-2025-62518)
Vulnerability from osv_ubuntu – Published: 2025-10-21 17:15 – Updated: 2026-05-20 15:22 – Source websiteastral-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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librust-astral-tokio-tar-dev",
"binary_version": "0.5.2-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "rust-astral-tokio-tar",
"purl": "pkg:deb/ubuntu/rust-astral-tokio-tar@0.5.2-2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.5.1-1",
"0.5.2-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librust-astral-tokio-tar-dev",
"binary_version": "0.5.6-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rust-astral-tokio-tar",
"purl": "pkg:deb/ubuntu/rust-astral-tokio-tar@0.5.6-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.5.2-2",
"0.5.5-1",
"0.5.6-1",
"0.5.6-2"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2025-62518",
"modified": "2026-05-20T15:22:57Z",
"published": "2025-10-21T17:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2025-62518"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-62518"
},
{
"type": "REPORT",
"url": "https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-j5gw-2vrg-8fgx"
},
{
"type": "REPORT",
"url": "https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318"
},
{
"type": "REPORT",
"url": "https://edera.dev/stories/tarmageddon"
},
{
"type": "REPORT",
"url": "https://github.com/edera-dev/cve-tarmageddon"
},
{
"type": "REPORT",
"url": "https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318"
},
{
"type": "REPORT",
"url": "https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2025-62518"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.