undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation

Summary

undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici's established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. 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. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.

Timeline

1. Oct 15, 2026, 6:38 PM UTCCVE published
2. Oct 16, 2026, 8:01 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Oct 16, 2026, 8:01 PM UTCRecord last updated

Affected versions

• undici undici

  From 4.2.1 · fixed in 6.29.1; From 7.0.0 · fixed in 7.30.1; From 8.0.0 · fixed in 8.12.2

• undicinpm

  From 4.2.1 · fixed in 6.29.1

• undicinpm

  From 7.0.0 · fixed in 7.30.1

• undicinpm

  From 8.0.0 · fixed in 8.12.2

References 2