CVE-2026-24842 affects node-tar (npm package "tar") versions prior to 7.5.7. The flaw is in handling TAR hardlink entries during extraction: the security validation for hardlink targets uses different path resolution semantics than the logic that actually creates the hardlink. Because of this mismatch, a crafted archive can bypass the intended path traversal protections. An attacker can supply a malicious TAR containing hardlink entries that resolve outside the designated extraction root, causing node-tar to create hardlinks to arbitrary filesystem locations outside the extraction directory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
File inclusion vulnerability in the node-tar dependency affecting Confluence Data Center.
A path traversal / arbitrary file write (via hardlink creation) issue in node-tar where inconsistent path resolution between validation and extraction allows a crafted TAR to create hardlinks to files outside the intended extraction directory.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.