En bref
- CVE-2026-109869 est une vulnérabilité ÉLEVÉE (CVSS 7.5) touchant undici (nodejs), undici.
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.34%, plus élevée que 27.9% des vulnérabilités.
- Correctif : mettre à jour vers 6.29.1, 7.30.1, 8.12.2 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| undici | ≥ 6.23.0, < 6.29.1≥ 7.18.0, < 7.30.1≥ 8.0.0, < 8.12.2
| 6.29.17.30.18.12.2
|
| undici npm | ≥ 6.23.0, < 6.29.1≥ 7.18.0, < 7.30.1≥ 8.0.0, < 8.12.2
| 6.29.17.30.18.12.2
|
Description
Impact
undici's fetch() crashes the Node.js process when a malicious server returns a response with more than five content codings and closes the connection before sending the body. undici rejects such responses (a content-encoding limit), but it created the internal response stream before that check and returned without attaching an error listener or aborting the request. The early close then surfaces a content-length mismatch on that orphaned internal stream, which Node.js treats as an unhandled error and terminates the process. A remote, unauthenticated server can trigger this with a single response, even when the application correctly catches the fetch() rejection. undici 6.x, 7.x, and 8.x are affected.
Patches
Upgrade to 6.29.1, 7.30.1, or 8.12.2. undici now validates the content-encoding chain before creating the internal body stream and aborts the response when the limit is exceeded, so no error can surface on an orphaned stream.
Workarounds
None.
NVD description
undici is an HTTP client library for Node.js. In versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, and 8.0.0 through 8.12.1, its fetch() implementation crashes the Node.js process when a malicious server returns a response with more than five content codings and closes the connection before sending the body. undici rejects such responses because of a content-encoding limit, but it created the internal response stream before that check and returned without attaching an error listener or aborting the request, so the early close surfaces a content-length mismatch on the orphaned stream, which Node.js treats as an unhandled error and terminates the process. A remote, unauthenticated server can trigger this with a single response, even when the application correctly catches the fetch() rejection, resulting in a denial of service. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. There is no workaround.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free