Skip to main content
VulnerabilityPublished

CVE-2026-59873: isaacs node-tar · Unthrottled Resource Allocation

Affects isaacs node-tarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.2 Critical : upgrade to 7.5.19 as a priority.

Data as of 20 Nov 2026, 17:35 UTC

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

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.19.

Affected software

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

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.19 or later, where the vulnerability is fixed by enforcing limits on decompressed data size, entry counts, and decompression ratio. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the description confirms the issue is fixed in 7.5.19. No other mitigations are indicated.

Description

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to exhaust disk space and CPU. This issue is fixed in version 7.5.19.

References

Community reviews

Loading reviews…