Skip to main content
VulnerabilityPublished Updated

CVE-2026-73566: isaacs node-tar · Uncontrolled Resource Consumption

Affects isaacs node-tarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 7.5.21 soon.

Data as of 10 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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 10 Nov 2026.

What to do

Upgrade isaacs node-tar to 7.5.21.

Affected software

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

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

AI-suggested

This vulnerability is fixed in node-tar version 7.5.21. Users should upgrade to version 7.5.21 or later to remediate the issue. No other mitigation or workaround is documented. Patch status is not explicitly stated but the fix is included in version 7.5.21, so upgrading to this version or newer is the recommended remediation.

Description

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.21, node-tar's filesFilter in src/list.ts uses the recursive mapHas helper to walk an archive entry path upward with path.dirname() and no segment cap when tar.t(...) or tar.x(...) receives a non-empty member-selection list. A crafted GNU L or PAX x long-path header with thousands of slash-separated segments reaches this.filter(entry.path, entry) in Parser[CONSUMEHEADER] in src/parse.ts before Unpack[CHECKPATH] applies maxDepth, causing an uncatchable RangeError stack overflow that terminates asynchronous and streaming Node.js consumers. This issue is fixed in version 7.5.21.

References

Community reviews

Loading reviews…