Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24884: CWE-59: Improper Link Resolution Before File Access ('Link Following') in node-modules compressing

0
High
VulnerabilityCVE-2026-24884cvecve-2026-24884cwe-59
Published: Wed Feb 04 2026 (02/04/2026, 19:35:56 UTC)
Source: CVE Database V5
Vendor/Project: node-modules
Product: compressing

Description

CVE-2026-24884 is a high-severity vulnerability in the node-modules 'compressing' library versions 2. 0. 0 and prior to 1. 10. 4. The flaw involves improper link resolution during TAR archive extraction, where symbolic links are restored without validating their targets. This allows attackers to craft archives with symlinks pointing outside the intended extraction directory, enabling arbitrary file writes or overwrites on the host system. Exploitation can lead to full confidentiality, integrity, and availability compromise without requiring authentication or user interaction. The vulnerability has been patched in versions 1. 10.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/12/2026, 07:39:57 UTC

Technical Analysis

CVE-2026-24884 is a vulnerability classified under CWE-59 (Improper Link Resolution Before File Access) affecting the 'compressing' library for Node.js, specifically versions 2.0.0 and all versions prior to 1.10.4. The vulnerability arises during the extraction of TAR archives where the library restores symbolic links without validating whether these links point within the intended extraction directory. An attacker can embed malicious symlinks in a crafted TAR archive that resolve to locations outside the extraction root. When the archive is extracted, subsequent file entries can be written to arbitrary locations on the host filesystem, potentially overwriting sensitive files or creating new files in security-critical directories. This can lead to privilege escalation, code execution, or denial of service depending on the files affected. The vulnerability does not require any privileges or user interaction to exploit, making it highly dangerous in automated or unattended extraction scenarios. The CVSS v3.1 base score is 8.4, indicating high severity with impacts on confidentiality, integrity, and availability. The issue has been addressed in versions 1.10.4 and 2.0.1 of the compressing library, where proper validation of symbolic link targets during extraction has been implemented to prevent directory traversal and arbitrary file writes.

Potential Impact

For European organizations, this vulnerability poses significant risks especially for those relying on Node.js applications that use the 'compressing' library for handling TAR archives. Exploitation can lead to unauthorized overwriting of critical system or application files, potentially resulting in data breaches, service disruption, or full system compromise. Organizations in sectors such as finance, healthcare, government, and critical infrastructure are particularly at risk due to the sensitivity of their data and the criticality of their systems. Automated deployment pipelines, CI/CD systems, or any service that extracts TAR archives without strict validation could be leveraged by attackers to implant malicious files or disrupt operations. The vulnerability's ability to affect confidentiality, integrity, and availability simultaneously makes it a severe threat to operational continuity and regulatory compliance under GDPR and other European data protection laws.

Mitigation Recommendations

European organizations should immediately audit their software dependencies to identify usage of the 'compressing' library versions 2.0.0 or any version prior to 1.10.4. They must upgrade to version 1.10.4 or 2.0.1 or later where the vulnerability is patched. Additionally, implement strict input validation and sandboxing for archive extraction processes to restrict file writes to intended directories. Employ runtime monitoring to detect anomalous file system changes during extraction. Where upgrading is not immediately feasible, consider isolating the extraction process in containers or virtual machines with limited permissions to minimize potential damage. Security teams should also review logs for suspicious extraction activities and educate developers about secure handling of archive files. Incorporating static and dynamic analysis tools to detect unsafe archive extraction patterns in codebases can prevent future vulnerabilities of this nature.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-27T19:35:20.527Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983a549f9fa50a62fa8d0c5

Added to database: 2/4/2026, 8:00:09 PM

Last enriched: 2/12/2026, 7:39:57 AM

Last updated: 3/22/2026, 5:07:12 AM

Views: 33

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses