Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 5.3, published 29 September 2026.
- Which products and versions are affected?
- adm-zip (npm) <= 0.6.0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run Adm-Zip or adm-zip (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The synchronous getData() path enforces a maxOutputLength guard against decompression bombs by passing the limit to Node's inflateRawSync(), but the asynchronous getDataAsync() path fails to enforce the same limit when using createInflateRaw(), instead accumulating all decompressed chunks into memory regardless of the declared size. An attacker can craft a ZIP file with a small declared uncompressed size but a high-compression-ratio payload that decompresses to gigabytes of data, bypassing application-level size checks.
Affected products
- adm-zip adm-zip
Timeline
- 2026-09-29: disclosed