CVE Catalog

CVE-2026-53600

MediumCVSS 6.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.32%

25th percentile - higher than 25% of all known CVEs

Summary

The async-tar library for async Rust before version 0.6.1 mis-applies a buffered PAX size extension to an intermediary extension header (GNU longname L, GNU longlink K, or PAX x/g) instead of to the next file entry. This desynchronizes the parser relative to a POSIX-correct tar parser (e.g., GNU tar), reading subsequent bytes at the wrong block boundary.

Risk Assessment

An attacker can craft a malicious tar archive that, when processed by async-tar, may lead to incorrect data reading or potentially other issues such as information disclosure or application crash.

Recommendation

Update the async-tar library to version 0.6.1 or later, which includes the fix. Avoid processing untrusted tar archives until updated.

Related vulnerabilities

Original NVD description (English source)

async-tar is a tar archive reading/writing library for async Rust. Prior to version 0.6.1, async-tar mis-applies a buffered PAX size extension to an intermediary extension header (a GNU longname L, a GNU longlink K, or a PAX x/g header) instead of to the next file entry. POSIX requires a PAX extended-header record set to describe the next file entry, never an intervening extension header. Because poll_next_raw (src/archive.rs) threads the buffered PAX records into the size computation of whatever raw header it reads next — and that header can be an intermediary L — the stream cursor is advanced by an attacker-chosen amount when the L body is consumed. The parser then desyncs relative to a POSIX-correct tar parser (e.g. GNU tar), reading subsequent bytes at the wrong block boundary. This issue has been patched in version 0.6.1.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS