Quick answers
- Is CVE-2026-39246 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39246 being exploited in the wild.
- How severe is CVE-2026-39246?
- Informational severity, with a CVSS score of 0, published 9 July 2026.
- Which products and versions are affected?
- Kevin Mårtensson Decompress < 4.2.2.
- Is there a fix for CVE-2026-39246?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-39246 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-39246?
- Check whether you run Kevin Mårtensson Decompress at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The 'decompress' package fails to validate the target of symbolic link entries during archive extraction. While the library includes a 'preventWritingThroughSymlink' check, this validation is only applied to file entries and not to the creation of the symlinks themselves. In 'index.js', the 'x.linkname' field from the archive is passed directly to 'fs.symlink()' without ensuring the target resides within the intended destination directory. An attacker can exploit this by crafting an archive containing a symlink that points to sensitive system files (e.g., /etc/passwd); if the application subsequently reads the extracted content, it will follow the link and disclose the contents of the target file.
Affected products
- kevva decompress < 4.2.2
Timeline
- 2026-07-04: disclosed: Issue reported on GitHub by devploit
- 2026-07-09: advisory: CVE published by NVD