CVE-2026-24842
EUVD-2026-490928.01.2026, 01:16
node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory. Version 7.5.7 contains a fix for the issue.
Affected Products (NVD)
| Vendor | Product | Version |
|---|---|---|
| isaacs | tar | 𝑥 < 7.5.7 |
𝑥
= Vulnerable software versions
Debian Releases
Ubuntu Releases
Red Hat Enterprise Linux Releases
Amazon Linux Releases
Amazon Package | |||
|---|---|---|---|
| nodejs24 |
| ||
| nodejs24-debuginfo |
| ||
| nodejs24-debugsource |
| ||
| nodejs24-devel |
| ||
| nodejs24-docs |
| ||
| nodejs24-full-i18n |
| ||
| nodejs24-libs |
| ||
| nodejs24-libs-debuginfo |
| ||
| nodejs24-npm |
| ||
| v8-13.6-devel |
|
Common Weakness Enumeration
- CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
- CWE-59 - Improper Link Resolution Before File Access ('Link Following')The software attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
References