Disclosure summary
### Impact The `interceptors.decompress()` interceptor decompresses HTTP response bodies according to the untrusted `Content-Encoding` header. The number of decompression layers is capped at 5, but the total decompressed output size is not bounded and there is no option to limit it. A malicious or faulty upstream can return a small compressed payload (a compression bomb) that expands to hundreds of megabytes or gigabytes in client memory, exhausting memory and causing the Node.js process to crash or become unresponsive. Any application using the decompress interceptor to read responses from untrusted or compromised upstreams is affected. ### Patches Upgrade to `7.29.1` or `8.10.2`. The interceptor now accepts a `maxSize` option (default 64 MiB) and rejects responses whose decompressed output exceeds it with a `ResponseExceededMaxSizeError`. ### Workarounds Once upgraded, set a conservative `maxSize` on the interceptor. Before upgrading, avoid using `interceptors.decompress()` with untrusted upstreams, or apply a custom interceptor that enforces a decompressed output size limit.
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
GitHub Reviewed Security Advisories · GHSA-3xpg-4rpp-hhhm
Open original source · Updated Sep 29, 2026
undici vulnerable to Denial of Service via unbounded decompression of compressed responses
Source severity: MEDIUM / 0
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| npm | undici | >= 7.15.0, < 7.29.1 | 7.29.1 |
| npm | undici | >= 8.0.0, < 8.10.2 | 8.10.2 |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Reviewed advisory
PUBLISHED 2026-09-29T14:20:37-04:00
MODIFIED 2026-09-29T14:20:38-04:00
INGESTED 2026-10-06T11:43:08-04:00