CVE-2026-39243: decompress allows arbitrary hardlink creation during archive extraction
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).
Published Jul 10, 2026 · Updated Aug 13, 2026
Affected packages
decompress
- Ecosystem
- npm
- Affected
- <= 4.2.1
- Fixed in
- No patched version yet
- Check
npm ls decompress
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-101894
@xhmikosr/decompress: Path traversal via symlink chain
critical9.1No fixSep 29, 2026CVE-2026-53486
Decompress: Archive extraction can create files and links outside of the target directory
critical9.1No fixJul 6, 2026CVE-2026-10732
decompress: Arbitrary File Write via Archive Extraction (Zip Slip)
medium6.4No fixJun 5, 2026
