Description
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.
Affected products
decompress_project: decompress
References4
- github.com/kevva/decompress/issues/113 ExploitVendor Advisory
- github.com/kevva/decompress/issues/113 ExploitVendor Advisory
- github.com/kevva/decompress Product
- www.npmjs.com/package/decompress Product
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 23 · as of 15 November 2026
- CWE
- CWE-59
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.