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.
CVE-2026-53600
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 59(Attend)EG Risk 59/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
September 9, 2026
Advisory Details (2)
Auto-updated Sep 2, 2026async-tar PAX extension-header desync enables tar entry/content smuggling · Advisory · dignifiedquire/async-tar · GitHub
https://github.com/dignifiedquire/async-tar/security/advisories/GHSA-35rm-7j9c-2f7mv0.6.1
Patch available: dignifiedquire/async-tar v0.6.1
https://github.com/dignifiedquire/async-tar/releases/tag/v0.6.1Vendor Advisories for CVE-2026-53600(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| async-tar | — | 0.6.1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust-async-tar | 0.4.2-2 | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:42 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 07:48 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:23 UTCEG score recompute
- 2026-09-12 03:31 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 22:57 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 22:46 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 19:57 UTCEG score recompute
- 2026-09-02 16:18 UTCEG score recompute▲ 6.30
- 2026-09-02 16:16 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
- 2026-08-01 03:43 UTCEG score recompute
- 2026-07-26 12:25 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-08 20:46 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p95HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p92HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-53600?
When was CVE-2026-53600 disclosed?
Is CVE-2026-53600 actively exploited?
What is the CVSS score of CVE-2026-53600?
How do I remediate CVE-2026-53600?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53600
Is Your Infrastructure Affected by CVE-2026-53600?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.