decompress before 4.2.2 allows arbitrary hardlink creation during archive extraction, enabling file read disclosure and file corruption. When processing hardlink entries (type === 'link'), the x.linkname field from the archive is passed directly to fs.link() without validation (index.js line 113). An attacker can craft an archive with a hardlink entry whose linkname is an absolute path to any file on the same filesystem. This creates a hardlink inside the extraction directory that shares the same inode as the target file, enabling both reading and overwriting the original file's content. Hardlinks are limited to files on the same filesystem and cannot target directories.
CVE-2026-39243
Score 5.5 from GitHub Security Advisory published 2026-07-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity55% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 13, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026[CVE-2026-39243] Arbitrary hardlink creation during extraction → file read disclosure & corruption · Issue #113 · kevva/decompress · GitHub
https://github.com/kevva/decompress/issues/113GitHub - kevva/decompress: Extracting archives made easy · GitHub
https://github.com/kevva/decompressVendor Advisories for CVE-2026-39243(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | dotnet8-0-main-8.0.128-1.1.hum1 | 2026-07-10 | redhat |
| npm | decompress | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 114× 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 162 total refreshes for this CVE.
- 2026-08-30 06:59 UTCEG score recompute
- 2026-08-30 06:59 UTCVendor advisory
- 2026-08-30 06:59 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 02:43 UTCEG score recompute
- 2026-08-28 02:43 UTCVendor advisory
- 2026-08-28 02:43 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 03:11 UTCEG score recompute
- 2026-08-27 03:11 UTCVendor advisory
- 2026-08-27 03:11 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 04:03 UTCEG score recompute
- 2026-08-26 04:03 UTCVendor advisory
- 2026-08-26 04:02 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:44 UTCEG score recompute
- 2026-08-24 21:44 UTCVendor advisory
- 2026-08-24 21:44 UTCGHSA enrichment
- 2026-08-23 22:19 UTCEG score recompute
- 2026-08-23 22:19 UTCVendor advisory
- 2026-08-23 22:19 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 23:06 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 23:06 UTCGHSA enrichment
- 2026-08-22 00:02 UTCEG score recompute
- 2026-08-22 00:02 UTCVendor advisory
- 2026-08-22 00:02 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 00:58 UTCEG score recompute
- 2026-08-21 00:58 UTCVendor advisory
- 2026-08-21 00:58 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 01:54 UTCEG score recompute
- 2026-08-20 01:54 UTCVendor advisory
- 2026-08-20 01:54 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 22:27 UTCEG score recompute
- 2026-08-18 22:27 UTCVendor advisory
- 2026-08-18 22:27 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:20 UTCEG score recompute
- 2026-08-17 22:20 UTCVendor advisory
- 2026-08-17 22:19 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 19:37 UTCEG score recompute
- 2026-08-16 19:37 UTCVendor advisory
- 2026-08-16 19:37 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:17 UTCEG score recompute
- 2026-08-15 20:17 UTCVendor advisory
- 2026-08-15 20:17 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:13 UTCVendor advisory
- 2026-08-14 21:13 UTCGHSA enrichment
- 2026-08-13 22:09 UTCEG score recompute
- 2026-08-13 22:09 UTCVendor advisory
- 2026-08-13 22:09 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:05 UTCEG score recompute
- 2026-08-12 23:05 UTCVendor advisory
- 2026-08-12 23:05 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 00:02 UTCEG score recompute
- 2026-08-12 00:02 UTCVendor advisory
- 2026-08-12 00:02 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 00:58 UTCEG score recompute
- 2026-08-11 00:58 UTCVendor advisory
- 2026-08-11 00:58 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 01:54 UTCEG score recompute
- 2026-08-10 01:54 UTCVendor advisory
- 2026-08-10 01:54 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:51 UTCEG score recompute
- 2026-08-09 02:51 UTCVendor advisory
- 2026-08-09 02:51 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:48 UTCEG score recompute
- 2026-08-08 03:48 UTCVendor advisory
- 2026-08-08 03:48 UTCGHSA enrichment
- 2026-08-07 04:44 UTCEG score recompute
- 2026-08-07 04:44 UTCVendor advisory
- 2026-08-07 04:44 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 05:41 UTCEG score recompute
- 2026-08-06 05:41 UTCVendor advisory
- 2026-08-06 05:41 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 06:37 UTCEG score recompute
- 2026-08-05 06:37 UTCVendor advisory
- 2026-08-05 06:37 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 05:53 UTCEG score recompute
- 2026-08-04 05:53 UTCVendor advisory
- 2026-08-04 05:53 UTCGHSA enrichment
Related CVEs(same product + same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-39243?
When was CVE-2026-39243 disclosed?
Is CVE-2026-39243 actively exploited?
What is the CVSS score of CVE-2026-39243?
How do I remediate CVE-2026-39243?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-39243
Is Your Infrastructure Affected by CVE-2026-39243?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.