CVE-2026-33055

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
67(Attend)
EG Risk 67/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 computed
Severity81% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic
https://www.cve.org/CVERecord?id=CVE-2025-62518
github Patch Available🟡 PoC Available

tar-rs incorrectly ignores PAX size headers if header size is nonzero · Advisory · composefs/tar-rs · GitHub

https://github.com/alexcrichton/tar-rs/security/advisories/GHSA-gchp-q4r4-x4ff
github_commit Patch Available

commit de1a5870e603 (alexcrichton/tar-rs)

Patch available: alexcrichton/tar-rs 0.4.46 (contains commit de1a5870e603)

https://github.com/alexcrichton/tar-rs/commit/de1a5870e603758f430073688691165f21a33946

Vendor Advisories for CVE-2026-33055(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(9 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
rustc1.48.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (200 versions)——
rust-tar0.4.26-1 ... 0.4.45-2 (14 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
rustc1.63.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (144 versions)——
rust-tar0.4.38-1 ... 0.4.45-2 (10 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
rustc1.85.0+dfsg3-1 ... 1.96.0+dfsg1-1~exp1 (50 versions)——
rust-tar0.4.43-4, 0.4.44-1, 0.4.45-1, 0.4.45-2——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
rustc1.85.0+dfsg3-1 ... 1.92.0+dfsg1-2~bpo13+1 (34 versions)1.92.0+dfsg1-2—
rust-tar0.4.43-4, 0.4.44-10.4.45-1—
crates.io(1)
PackageVulnerable rangeFixed inDependents
tar—0.4.45—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 48× 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.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:17 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 11:00 UTCEG score recompute
  13. 2026-08-16 11:00 UTCVendor advisory
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 19:49 UTCVendor advisory
  17. 2026-08-14 07:11 UTCEG score recompute
  18. 2026-08-14 07:11 UTCVendor advisory
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 21:52 UTCEG score recompute
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 21:23 UTCEG score recompute
  23. 2026-08-11 21:23 UTCVendor advisory
  24. 2026-08-11 04:24 UTCEG score recompute
  25. 2026-08-11 04:24 UTCVendor advisory
Show 75 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-10 04:27 UTCVendor advisory
  3. 2026-08-09 17:36 UTCEG score recompute
  4. 2026-08-09 17:36 UTCVendor advisory
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-09 06:45 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 17:14 UTCEG score recompute
  9. 2026-08-07 17:14 UTCVendor advisory
  10. 2026-08-06 19:18 UTCEG score recompute
  11. 2026-08-06 19:18 UTCVendor advisory
  12. 2026-08-06 13:46 UTCEPSS rescore
  13. 2026-08-06 01:27 UTCEG score recompute
  14. 2026-08-06 01:27 UTCVendor advisory
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:38 UTCEPSS rescore
  18. 2026-08-02 16:11 UTCEG score recompute
  19. 2026-08-02 16:11 UTCVendor advisory
  20. 2026-08-02 02:27 UTCEPSS rescore
  21. 2026-08-01 04:16 UTCEPSS rescore
  22. 2026-07-30 16:28 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-27 14:13 UTCEPSS rescore
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 03:09 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-21 15:24 UTCEPSS rescore
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-17 07:46 UTCOSV refresh
  40. 2026-07-16 17:03 UTCEPSS rescore
  41. 2026-07-16 17:03 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 02:00 UTCEPSS rescore
  45. 2026-07-15 02:00 UTCEPSS rescore
  46. 2026-07-13 22:30 UTCEPSS rescore
  47. 2026-07-13 06:13 UTCEPSS rescore
  48. 2026-07-13 06:13 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-09 19:10 UTCEPSS rescore
  52. 2026-07-08 15:15 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-06 02:23 UTCEPSS rescore
  58. 2026-07-05 02:30 UTCEPSS rescore
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-29 14:06 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 05:32 UTCOSV refresh
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 14:07 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-25 13:49 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-24 14:05 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 21:33 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33055?
CVE-2026-33055 is a high vulnerability published on March 20, 2026. tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the…
When was CVE-2026-33055 disclosed?
CVE-2026-33055 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33055 actively exploited?
CVE-2026-33055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.4% of all scored CVEs.
What is the CVSS score of CVE-2026-33055?
CVE-2026-33055 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-33055?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33055, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-33055?

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

Start Free Scan →Browse All CVEs