Skip to main content
VulnerabilityPublished

CVE-2026-59875: isaacs node-tar · Uncaught Exception

Affects isaacs node-tarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 7.5.17 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.5.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 20 Nov 2026.

What to do

Upgrade isaacs node-tar to 7.5.17.

Affected software

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

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

AI-suggested

Upgrade node-tar to version 7.5.17 or later, where this issue is fixed by stripping NUL bytes from PAX path and linkpath records. No other mitigations are indicated.

Description

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.17, node-tar does not strip NUL bytes from PAX path and linkpath records in src/pax.ts, allowing a crafted archive with values to reach fs.lstat or fs.open and terminate the process with an uncaught exception. This issue is fixed in version 7.5.17.

References

Community reviews

Loading reviews…