Description
The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction can create files and links outside the target directory. When extracting an archive to a directory, a crafted archive can read or write files outside that directory because hardlink and symlink entries are created without checking where targets point, path containment used a string prefix comparison, and file modes failed to remove setuid, setgid, or sticky bits. This issue is fixed in @xhmikosr/decompress versions 10.2.1 and 11.1.3.
References7
- github.com/XhmikosR/decompress/commit/281cefa00cd4275c10479bc5f…
- github.com/XhmikosR/decompress/commit/60b5299402e72b0b53ca2e552…
- github.com/XhmikosR/decompress/commit/9fcda4b0a66ca22dc8d337f9b…
- github.com/XhmikosR/decompress/commit/aca5aac415dc04a6fae5200e5…
- github.com/XhmikosR/decompress/releases/tag/v10.2.1
- github.com/XhmikosR/decompress/releases/tag/v11.1.3
- github.com/XhmikosR/decompress/security/advisories/GHSA-mp2f-45…
Metrics
- CVSS 3.1
-
9.1
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 1% percentile: 56 · as of 15 November 2026
- CWE
- CWE-22CWE-59CWE-732
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.