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.
CVE-2026-59873
CRITICALPre-NVD 9.29.2Elevated
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
9.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 9.2Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.2
- EG Score
- 9.2(low)
- EPSS
- —
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 8, 2026
Advisory Details (2)
Auto-updated Jul 8, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available
Decompression/parse DoS via unlimited input · Advisory · isaacs/node-tar · GitHub
https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpwgithub_commit
commit 2812e9338665 (isaacs/node-tar)
Fix landed in isaacs/node-tar commit 2812e9338665 — awaiting tagged release
https://github.com/isaacs/node-tar/commit/2812e9338665659b183aa7226518c307044957d3Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 15:46 UTCEG score recompute
- 2026-07-08 15:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-59873?
CVE-2026-59873 is a critical vulnerability published on July 8, 2026. 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…
When was CVE-2026-59873 disclosed?
CVE-2026-59873 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-59873?
CVE-2026-59873 has a CVSS v3 base score of 9.2 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59873, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59873
Is Your Infrastructure Affected by CVE-2026-59873?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.