CVE-2026-39246: n/a
decompress before 4.2.2 allows arbitrary symlink creation during archive extraction. When processing symlink entries (type === 'symlink'), the x.linkname field from the archive is passed directly to fs.symlink() without validation (index.js line 121). The preventWritingThroughSymlink check on line 98 only applies to file entries, not symlink creation. An attacker can craft an archive with symlink entries pointing to sensitive files outside the extraction directory (e.g., /etc/passwd), enabling information disclosure when the application reads the extracted contents.
AI Analysis
Technical Summary
The decompress library prior to version 4.2.2 improperly handles symbolic link entries during archive extraction. Specifically, the x.linkname field from symlink entries is passed directly to fs.symlink() without validation, while the existing preventWritingThroughSymlink check only applies to file entries, not symlink creation. This allows an attacker to craft archives with symlinks pointing to arbitrary locations outside the extraction directory, potentially exposing sensitive files such as /etc/passwd when the application accesses the extracted contents.
Potential Impact
An attacker can create archives containing symbolic links that point to sensitive files outside the intended extraction directory. When the application extracts and subsequently reads these symlinked files, it may disclose sensitive information. The vulnerability does not affect confidentiality directly through the extraction process but enables indirect information disclosure via crafted archives.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid extracting untrusted archives with decompress versions prior to 4.2.2 or implement additional validation to prevent symlink creation outside the extraction directory.
CVE-2026-39246: n/a
Description
decompress before 4.2.2 allows arbitrary symlink creation during archive extraction. When processing symlink entries (type === 'symlink'), the x.linkname field from the archive is passed directly to fs.symlink() without validation (index.js line 121). The preventWritingThroughSymlink check on line 98 only applies to file entries, not symlink creation. An attacker can craft an archive with symlink entries pointing to sensitive files outside the extraction directory (e.g., /etc/passwd), enabling information disclosure when the application reads the extracted contents.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The decompress library prior to version 4.2.2 improperly handles symbolic link entries during archive extraction. Specifically, the x.linkname field from symlink entries is passed directly to fs.symlink() without validation, while the existing preventWritingThroughSymlink check only applies to file entries, not symlink creation. This allows an attacker to craft archives with symlinks pointing to arbitrary locations outside the extraction directory, potentially exposing sensitive files such as /etc/passwd when the application accesses the extracted contents.
Potential Impact
An attacker can create archives containing symbolic links that point to sensitive files outside the intended extraction directory. When the application extracts and subsequently reads these symlinked files, it may disclose sensitive information. The vulnerability does not affect confidentiality directly through the extraction process but enables indirect information disclosure via crafted archives.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid extracting untrusted archives with decompress versions prior to 4.2.2 or implement additional validation to prevent symlink creation outside the extraction directory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-06T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a50171468715ace431ea193
Added to database: 07/09/2026, 21:48:04 UTC
Last enriched: 07/17/2026, 09:45:12 UTC
Last updated: 08/22/2026, 22:52:13 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.