@xhmikosr/decompress: Path traversal via symlink chain
XhmikosR decompress · kevva decompress
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xhmikosr/decompress npm |
|
|
| decompress npm |
| No fix yet |
XhmikosR decompress · kevva decompress
| Product | Affected | Fixed in |
|---|---|---|
| @xhmikosr/decompress npm |
|
|
| decompress npm |
| No fix yet |
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
From the CVE record · GitHub_M
The default decompress(input, output) API can follow symlink chains in a crafted archive past its output directory. When an application extracts an attacker-supplied archive, this can let the attacker read or write files outside that directory; overwriting startup scripts or configuration can lead to remote code execution.
Check applications using npm @xhmikosr/decompress versions below 10.2.2 or from 11.0.0 through 11.1.3, or npm decompress versions through 4.2.1.