Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-59873: Gzip Bomb Denial of Service in node-tar

Published Jul 8, 2026 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS9.2Critical · v4
EPSS0.58%48th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Isaacs
IdentifiersCVE-2026-59873CWE-409

CVE-2026-59873 is a resource-exhaustion vulnerability in node-tar, a tar archive manipulation library for Node.js, affecting versions before 7.5.19. Archive extraction and parsing do not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio. A small, specially crafted gzip-compressed archive can therefore trigger excessive expansion and processing, exhausting disk space and CPU and causing denial of service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can exhaust disk capacity and CPU resources, causing application crashes, prolonged unavailability, or system-wide denial of service. Other services sharing the affected resources may also become unavailable. No confidentiality or integrity impact is established.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid processing untrusted archives with vulnerable node-tar versions unless external safeguards are enforced. Limit decompressed output size, archive entry counts, and decompression ratios; compressed-input size limits alone are insufficient. Use disk quotas and sandbox resource controls to constrain the effects of excessive expansion and CPU consumption.

Remediation

Patch, then assume compromise.

Upgrade the npm package tar (node-tar) to version 7.5.19 or later. Where node-tar is bundled within another product or operating-system package, apply the corresponding vendor-supported security update or backported fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IsaacsTarapplication
FAQ

Frequently asked questions

Is CVE-2026-59873 exploited in the wild?
As of Nov 9, 2026, Mallory has no reports of CVE-2026-59873 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59873?
Yes. As of Nov 9, 2026, Mallory has reports of a public exploit for CVE-2026-59873.
Is there a patch for CVE-2026-59873?
Upgrade the npm package tar (node-tar) to version 7.5.19 or later. Where node-tar is bundled within another product or operating-system package, apply the corresponding vendor-supported security update or backported fix.
What products are affected by CVE-2026-59873?
Isaacs Tar.
How severe is CVE-2026-59873?
CVE-2026-59873 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 0.58% (48th percentile) as of Nov 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity12Community discussion across Reddit, Mastodon, and other social sources.