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

0
High
VulnerabilityCVE-2026-26960cvecve-2026-26960cwe-22
Published: Fri Feb 20 2026 (02/20/2026, 01:07:52 UTC)
Source: CVE Database V5
Vendor/Project: isaacs
Product: node-tar

Description

CVE-2026-26960 is a high-severity path traversal vulnerability in isaacs node-tar versions prior to 7. 5. 8. The flaw allows an attacker to craft malicious tar archives that create hardlinks inside the extraction directory pointing to files outside the intended extraction root. This enables arbitrary file read and write operations with the privileges of the extracting user. Exploitation requires user interaction to extract a malicious archive but does not require prior authentication. The vulnerability bypasses typical path protections, turning archive extraction into a direct filesystem access primitive. No known exploits are currently reported in the wild. The issue was fixed in node-tar version 7. 5.

AI-Powered Analysis

AILast updated: 02/20/2026, 01:46:41 UTC

Technical Analysis

CVE-2026-26960 is a path traversal vulnerability classified under CWE-22 affecting isaacs node-tar, a widely used Node.js library for handling tar archives. In versions 7.5.7 and earlier, when extracting tar archives using default options, an attacker can craft a malicious archive containing hardlinks that point to files outside the designated extraction directory. During extraction, node-tar fails to properly restrict these hardlinks, allowing the archive to create or overwrite arbitrary files on the filesystem with the privileges of the user performing the extraction. This bypasses normal path traversal protections that typically prevent files from being written outside the extraction root. The vulnerability enables an attacker to read or modify sensitive files, potentially leading to code execution or data corruption. Exploitation requires the victim to extract a malicious archive, so user interaction is necessary, but no authentication is required. The CVSS v3.1 score is 7.1 (high severity), reflecting high confidentiality and integrity impact, low attack complexity, no privileges required, and user interaction needed. The vulnerability was publicly disclosed on February 20, 2026, and fixed in node-tar version 7.5.8. No known exploits are reported in the wild yet, but the ease of exploitation and the widespread use of node-tar in Node.js applications make this a significant risk.

Potential Impact

The impact of CVE-2026-26960 is substantial for organizations relying on node-tar for archive extraction, especially in automated or server-side environments. Successful exploitation allows attackers to write or overwrite arbitrary files on the filesystem, potentially leading to unauthorized disclosure of sensitive information, modification or deletion of critical files, and in some cases, remote code execution if executable files or scripts are overwritten. This can compromise system integrity and confidentiality, disrupt application functionality, and facilitate further lateral movement within networks. Since node-tar is commonly used in Node.js applications and development pipelines worldwide, vulnerable systems may include web servers, CI/CD environments, and container build processes. The requirement for user interaction (extracting the malicious archive) limits automated exploitation but does not eliminate risk, particularly in environments processing untrusted archives. Organizations failing to update or implement controls risk data breaches, service disruptions, and reputational damage.

Mitigation Recommendations

To mitigate CVE-2026-26960, organizations should immediately upgrade all instances of node-tar to version 7.5.8 or later, where the vulnerability is fixed. Additionally, implement strict validation and sanitization of all tar archives before extraction, especially those from untrusted or external sources. Employ sandboxing or containerization to isolate extraction processes, limiting filesystem access and privileges of the extracting user. Avoid running extraction operations with elevated privileges. Monitor logs for suspicious archive extraction activities and unexpected file modifications. Incorporate integrity checks and digital signatures on archive files to ensure authenticity. For development pipelines, restrict dependencies and archive inputs to trusted sources only. Finally, educate developers and system administrators about the risks of extracting untrusted archives and enforce security best practices around archive handling.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-16T22:20:28.611Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6997b995d7880ec89b49375c

Added to database: 2/20/2026, 1:32:05 AM

Last enriched: 2/20/2026, 1:46:41 AM

Last updated: 2/20/2026, 2:34:26 AM

Views: 5

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