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-23745: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in isaacs node-tar

0
High
VulnerabilityCVE-2026-23745cvecve-2026-23745cwe-22
Published: Fri Jan 16 2026 (01/16/2026, 22:00:08 UTC)
Source: CVE Database V5
Vendor/Project: isaacs
Product: node-tar

Description

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.

AI-Powered Analysis

AILast updated: 01/24/2026, 19:57:03 UTC

Technical Analysis

CVE-2026-23745 is a path traversal vulnerability classified under CWE-22 affecting the node-tar library, a widely used tar archive utility for Node.js. Versions up to 7.5.2 fail to properly sanitize the linkpath attribute of Link (hardlink) and SymbolicLink entries when the preservePaths option is set to false, which is the default secure setting. This improper sanitization allows maliciously crafted tar archives to escape the intended extraction directory, enabling attackers to overwrite arbitrary files on the filesystem. The vulnerability enables two main attack vectors: arbitrary file overwrite via hardlinks and symlink poisoning through absolute symbolic link targets. Exploiting this flaw can compromise system integrity by modifying critical files or planting malicious symlinks that redirect legitimate processes to attacker-controlled files. The CVSS 4.0 score of 8.2 reflects a high severity due to the potential for significant impact on confidentiality and integrity, despite requiring user interaction and local access vector. No authentication or privileges are needed, increasing the risk in multi-user or shared environments. The vulnerability was publicly disclosed on January 16, 2026, and fixed in node-tar version 7.5.3. While no known exploits have been reported in the wild, the widespread use of node-tar in Node.js applications and development environments makes this a critical issue to address promptly.

Potential Impact

For European organizations, this vulnerability poses a substantial risk, especially for those relying on Node.js applications that utilize node-tar for archive extraction. Successful exploitation can lead to arbitrary file overwrites, potentially allowing attackers to modify configuration files, inject malicious code, or disrupt application functionality. This can result in data integrity loss, application downtime, and potential lateral movement within networks. Critical sectors such as finance, healthcare, and government services that depend on Node.js for backend services or DevOps pipelines could face operational disruptions and data breaches. The requirement for user interaction and local access somewhat limits remote exploitation but does not eliminate risk in environments where users handle untrusted archives or where attackers have gained limited access. Additionally, symlink poisoning can be leveraged to escalate privileges or evade detection by redirecting file operations to attacker-controlled locations. The absence of known exploits currently provides a window for mitigation, but the high severity score underscores the urgency for European organizations to act.

Mitigation Recommendations

European organizations should immediately upgrade all instances of node-tar to version 7.5.3 or later to remediate this vulnerability. Beyond patching, implement strict validation and sanitization of all archive files before extraction, especially those received from untrusted sources. Employ sandboxed or containerized environments for archive extraction to limit potential damage from malicious files. Enforce the principle of least privilege for users and processes handling archive extraction to reduce the impact of any successful exploit. Monitor file system changes and employ integrity verification tools to detect unauthorized modifications. Incorporate security awareness training for developers and system administrators about the risks of handling untrusted archives and the importance of timely patching. Finally, review and harden DevOps pipelines and CI/CD processes that utilize node-tar to prevent supply chain attacks leveraging this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-15T15:45:01.958Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 696ab9f0b22c7ad868fb1aa0

Added to database: 1/16/2026, 10:21:36 PM

Last enriched: 1/24/2026, 7:57:03 PM

Last updated: 2/7/2026, 12:30:21 PM

Views: 372

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 in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats