CVE-2026-29786: node-tar: Hardlink Path Traversal via Drive-Relative Linkpath
node-tar is a full-featured Tar for Node.js. Prior to version 7.5.10, tar can be tricked into creating a hardlink that points outside the extraction directory by using a drive-relative link target such as C:../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This issue has been patched in version 7.5.10.
Security readout for executives and security teams
Plain-English summary
A malicious tar archive can make vulnerable node-tar versions overwrite files outside the intended extraction folder. This creates a serious integrity risk for services, build systems, or developer tools that automatically unpack untrusted archives. Version 7.5.10 contains the patch.
Executive priority
Prioritize rapid remediation for internet-facing ingestion, CI/CD, package-processing, and automated extraction systems. Other deployments should follow normal high-severity patch timelines after confirming dependency reachability. Focus first on systems combining vulnerable versions, untrusted archives, and meaningful filesystem permissions.
Technical view
Before 7.5.10, node-tar improperly validates drive-relative hardlink targets such as Windows-style paths. During normal tar.x() extraction, a crafted archive can create a hardlink outside the working directory and overwrite an external file. The supplied CVSS 3.1 score is 8.6, reflecting low-complexity, unauthenticated integrity impact across a security boundary.
Likely exposure
Exposure is most likely where node-tar below 7.5.10 extracts attacker-controlled or externally supplied archives, especially in Windows environments where drive-relative paths apply. Internet reachability is not required if archives enter through uploads, packages, build inputs, automation, or other untrusted channels. The bundle does not identify specific downstream applications.
Exploitation context
The supplied evidence does not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires a crafted archive to be processed by vulnerable node-tar extraction. No exploit prevalence, public weaponization, or observed campaigns are documented in the provided sources.
Researcher notes
The issue maps to CWE-22 path traversal and CWE-59 link-following weaknesses. Its principal documented effect is arbitrary file overwrite outside the extraction directory, producing high integrity impact without claimed confidentiality or availability impact. The supplied bundle does not clarify platform breadth beyond the drive-relative path example or identify affected downstream products.
Mitigation direction
Upgrade node-tar to version 7.5.10 or later.
Identify and update vulnerable transitive dependencies through supported parent-package releases.
Restrict archive extraction to trusted inputs until upgrades are complete.
Run extraction with minimal filesystem permissions and isolate temporary working directories.
Validation and detection
Review manifests, lockfiles, and deployed dependency inventories for node-tar versions below 7.5.10.
Confirm production artifacts resolve node-tar to version 7.5.10 or later.
Identify workflows that extract uploaded, downloaded, packaged, or otherwise untrusted tar archives.
Verify extraction processes cannot modify sensitive files outside their designated working directories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.