{"id":"CVE-2025-62518","title":"astral-tokio-tar is a tar archive reading/writing library for async Rust","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 inco…","severity":"high","cvss":8.1,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","cwe":["CWE-843"],"published":"2025-10-21","updated":"2026-10-08","sourceUpdated":"2026-10-08T11:10:00.250","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-62518","references":[{"url":"https://edera.dev/stories/tarmageddon","label":"security-advisories@github.com"},{"url":"https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318","label":"security-advisories@github.com"},{"url":"https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-j5gw-2vrg-8fgx","label":"security-advisories@github.com"},{"url":"https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9","label":"security-advisories@github.com"},{"url":"https://github.com/edera-dev/cve-tarmageddon","label":"security-advisories@github.com"}],"tags":["nvd","exploit-available"],"epss":0.00703,"epssPercentile":0.51793,"exploits":{"github":2,"githubRepos":["https://github.com/edera-dev/cve-tarmageddon","https://github.com/AirineiAndrei/Tarmageddon-CVE-2025-62518-"],"checkedAt":"2026-10-08T11:32:03.413Z"},"exploitAvailable":true,"ingestedAt":"2026-10-08T11:31:27.456Z","slug":"CVE-2025-62518","body":"## Overview\n\nastral-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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":57,"depthScoreParts":{"impact":44.6,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[]}