undici vulnerable to HTTP header injection via Set-Cookie percent-decoding

Summary

Impact: undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 §5.4 does not specify any decoding and browsers do not decode either. Applications that parse a Set-Cookie header and then forward the parsed value into a response header (proxies, middleware, SSR frameworks) become vulnerable to HTTP response header injection: an attacker-controlled upstream can inject arbitrary Set-Cookie, Location, or Cache-Control headers into the application's downstream response, enabling session fixation, open redirect, or cache poisoning. Affected applications are those that use undici's cookie parsing (parseSetCookie, parseCookie, getSetCookies) and forward the parsed cookie value into a response header. This was introduced in undici 7.0.0 via PR #3789. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, do not forward values returned by parseSetCookie/parseCookie/getSetCookies directly into response headers; sanitize the value first to strip or reject CR, LF, NUL, ;, and = bytes.

Timeline

1. Jun 17, 2026, 4:56 PM UTCCVE published
2. Jun 17, 2026, 6:31 PM UTCCISA SSVC assessment

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

3. Jun 23, 2026, 4:12 PM UTCRecord last updated

Affected versions

• undici undici

  fixed in 6.26.0; From 7.0.0 · fixed in 7.28.0; From 8.0.0 · fixed in 8.5.0

• undicinpm

  fixed in 6.27.0

• undicinpm

  From 7.0.0 · fixed in 7.28.0

• undicinpm

  From 8.0.0 · fixed in 8.5.0

References 2