CVE-2026-53600

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
59
EG Risk 59/100

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 computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

async-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-2f7m
GitHub release Patch Available

v0.6.1

Patch available: dignifiedquire/async-tar v0.6.1

https://github.com/dignifiedquire/async-tar/releases/tag/v0.6.1

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
async-tar—
  • every version up to 0.6.1: fixed in 0.6.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-async-tar0.4.2-2
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-01 16:10 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-28 13:20 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 27 more
  1. 2026-09-24 11:47 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-09-23 06:05 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-09-18 05:42 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-09-14 07:48 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-09-13 08:23 UTCEG score recompute
  12. 2026-09-12 03:31 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-09-09 22:57 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-05 22:46 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-02 19:57 UTCEG score recompute
  22. 2026-09-02 16:18 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  23. 2026-09-02 16:16 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  24. 2026-08-01 03:43 UTCEG score recompute
  25. 2026-07-26 12:25 UTCEG score recompute
  26. 2026-07-23 03:19 UTCEG score recompute
  27. 2026-07-08 20:46 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53600?
CVE-2026-53600 is a medium-severity vulnerability; its CVE record was published on July 8, 2026. 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…
When was the CVE record for CVE-2026-53600 published?
The CVE record for CVE-2026-53600 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-53600 actively exploited?
CVE-2026-53600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53600?
CVE-2026-53600 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53600?
A fix for CVE-2026-53600 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53600 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53600

Explore →

Is Your Infrastructure Affected by CVE-2026-53600?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs