decompress before 4.2.2 allows arbitrary hardlink creation during archive extraction, enabling file read…
Historical advisory recorded 25 Oct 2026 09:17:18 UTC. Read the latest advisory.
nvd · CVE-2026-39243
Publisheddecompress 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.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-39243
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-59
Original publisher date fields
published: 2026-07-09T22:17:04.113
lastModified: 2026-07-13T12:57:34.913
1 source CPE criteria · context only
- cpe:2.3:a:decompress_project:decompress:*:*:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON