Advisory

GHSA-g9mf-h72j-4rw9

Also known as: CVE-2026-22036

Summary

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

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-01-14 21:06 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

undici

npm · All systems

Affected

  • introduced 7.0.0, fixed 7.18.2 (semver)

Fixed versions

7.18.2

Fix

undici

npm · All systems

Affected

  • introduced 0, fixed 6.23.0 (semver)

Fixed versions

6.23.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences