Skip to main content
CVE-2026-23745VulnerabilityPublished Updated

CVE-2026-23745: isaacs node-tar · Path Traversal

Affects isaacs node-tarSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High : upgrade to 7.5.3 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.5.3
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade isaacs node-tar to 7.5.3.

Affected software

ProductAffectedFixed in
isaacsnode-tarAffected
  • <7.5.3
Fixed in
  • 7.5.3
npmnode-tarpkg:npm/node-tarOther threatsAffected
  • <7.5.3
Fixed in
  • 7.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available in node-tar version 7.5.3. Users and vendors should upgrade to this version to remediate the issue. Red Hat advisories indicate that no suitable mitigation other than upgrading meets their criteria for ease of use and deployment. Therefore, upgrading to a fixed version is the recommended remediation.

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.

References

Community reviews

Loading reviews…