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 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Aug 4, 2026`unpack_in` can chmod arbitrary directories by following symlinks · Advisory · composefs/tar-rs · GitHub
https://github.com/alexcrichton/tar-rs/security/advisories/GHSA-j4xf-2g29-59phcommit 17b1fd84e632 (alexcrichton/tar-rs)
Patch available: alexcrichton/tar-rs 0.4.46 (contains commit 17b1fd84e632)
https://github.com/alexcrichton/tar-rs/commit/17b1fd84e632071cb8eef9d3709bf347bd266446Vendor 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.
Affected Packages
(14 across 10 ecosystems)
Debian:11(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rustc | 1.48.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (200 versions) | — | — |
| rust-tar | 0.4.26-1 ... 0.4.45-2 (14 versions) | — | — |
Debian:12(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rustc | 1.63.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (144 versions) | — | — |
| rust-tar | 0.4.38-1 ... 0.4.45-2 (10 versions) | — | — |
Debian:13(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rustc | 1.85.0+dfsg3-1 ... 1.96.0+dfsg1-1~exp1 (50 versions) | — | — |
| rust-tar | 0.4.43-4, 0.4.44-1, 0.4.45-1, 0.4.45-2 | — | — |
Debian:14(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rustc | 1.85.0+dfsg3-1 ... 1.92.0+dfsg1-2~bpo13+1 (34 versions) | 1.92.0+dfsg1-2 | — |
| rust-tar | 0.4.43-4, 0.4.44-1 | 0.4.45-1 | — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust | — | 1.78.0-r1 | — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust | — | 1.83.0-r1 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust | — | 1.87.0-r1 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust | — | 1.91.1-r1 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust | — | 1.94.0-r1 | — |
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | — | 0.4.45 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(5)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 30× 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 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 17:08 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 49 moreShow fewer
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:03 UTCEG score recompute
- 2026-08-16 11:03 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 07:14 UTCEG score recompute
- 2026-08-14 07:14 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:54 UTCEG score recompute
- 2026-08-12 21:54 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 04:26 UTCEG score recompute
- 2026-08-11 04:26 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 05:16 UTCEG score recompute
- 2026-08-10 05:16 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:47 UTCEG score recompute
- 2026-08-09 06:47 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 17:17 UTCEG score recompute
- 2026-08-07 17:17 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 01:29 UTCEG score recompute
- 2026-08-06 01:29 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 00:37 UTCEG score recompute
- 2026-08-04 00:37 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 16:14 UTCEG score recompute▲ 1.40
- 2026-08-02 16:14 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 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
See which npm, PyPI, Go, and Maven packages are affected by 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.