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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/isaacs/node-tar/commit/2812e9338665659b183aa7226518c307044957d3 Patch
- https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpw Exploit, Vendor Advisory
- https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpw Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.2 · isaacsNVD modified 2026-10-25 17:10
Affected (CPE criteria) 1
cpe:2.3:a:isaacs:tar:*:*:*:*:*:node.js:*:*
References 4
- https://github.com/isaacs/node-tar/commit/2812e9338665659b183aa7226518c307044957d3 Patch
- https://github.com/isaacs/node-tar/releases/tag/v7.5.19 Release Notes
- https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpw Exploit, Vendor Advisory
- https://github.com/isaacs/node-tar/security/advisories/GHSA-23hp-3jrh-7fpw Exploit, Vendor Advisory