tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.
CVE-2026-33056
This medium-severity CVE scores 5.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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.5
- EG Score
- 5.1(low)
- EG Risk
- 23(Track)EG Risk 23/100SSVC: Track
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 computedSeverity51% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
References (2)
- security-advisories@githubhttps://github.com/alexcrichton/tar-rs/commit/17b1fd84e632071cb8eef9d3709bf347bd266446
- security-advisories@githubhttps://github.com/alexcrichton/tar-rs/security/advisories/GHSA-j4xf-2g29-59ph
Vendor Advisories for CVE-2026-33056(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:51 UTCEG score recompute
- 2026-07-27 12:51 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-33056?
When was CVE-2026-33056 disclosed?
Is CVE-2026-33056 actively exploited?
What is the CVSS score of CVE-2026-33056?
How do I remediate CVE-2026-33056?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33056
Is Your Infrastructure Affected by CVE-2026-33056?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.