NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-22036: Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion

mediumCVSS 3.1 5.9GHSA-g9mf-h72j-4rw9

Impact The fetch() API supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, br). This is also supported by the undici decompress interceptor. However, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory…

Published Jan 14, 2026 · Updated Jan 22, 2026

Affected packages

undici

Ecosystem
npm
Affected
>= 7.0.0, < 7.18.2
Fixed in
7.18.2
Check
npm ls undici

undici

Ecosystem
npm
Affected
< 6.23.0
Fixed in
6.23.0
Check
npm ls undici

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The fetch() API supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, br). This is also supported by the undici decompress interceptor.

However, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation.

Patches

Upgrade to 7.18.2 or 6.23.0.

Workarounds

It is possible to apply an undici interceptor and filter long Content-Encoding sequences manually.

References

  • https://hackerone.com/reports/3456148
  • https://github.com/advisories/GHSA-gm62-xv2j-4w53
  • https://curl.se/docs/CVE-2022-32206.html

Credited to mcollina, illia-v.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries