14 matches found
CVE-2026-12151
The CVE affects the undici WebSocket client (and WebSocketStream API) where maxPayloadSize is enforced per-frame but there is no limit on the number of fragments in a message. A malicious server can send many small or empty continuation frames, each passing validation, causing unbounded memory gr...
CVE-2026-13697
Summary of a known vulnerability in undici (CVE-2026-13697) : The cache interceptor in undici mishandles degenerate private directives in Cache-Control, enabling two issues in shared mode. First, a response with malformed qualified private directives (for example, private="" or private=",") can b...
CVE-2026-9697
undici’s ProxyAgent drops the requestTls option when used with a SOCKS5 proxy (socks5:// or socks://), causing the HTTPS connection to rely on Node’s default trust store and ignore user-provided ca, cert, key, rejectUnauthorized, and servername. This allows any cert signed by a publicly trusted C...
CVE-2026-11525
The issue affects undici’s cookie parsing in Set-Cookie headers. The root cause is a permissive substring match for the SameSite attribute during parsing, accepting any value containing Strict, Lax, or None instead of enforcing a case-insensitive exact match per RFC 6265. This can cause downstrea...
CVE-2026-15157
undici is vulnerable to CRLF injection via a duck-typed blob-like request body’s type property when used as the Content-Type header on HTTP/1.1 dispatchers. Affected ranges: undici before 6.28.0; 7.0.0–before 7.29.0; and 8.0.0–before 8.9.0. An attacker supplying a hand-rolled blob-like body deriv...
CVE-2026-16728
Undici contains a defect in its retry interceptor: after a retry or resume of a partial response, it can assemble a body whose length differs from the Content-Length observed by the application. In affected ranges (before 6.28.0, 7.0.0–7.28.x, and 8.0.0–7.29.0 to 8.8.x), a faulty upstream may ret...
CVE-2026-16729
undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields. In undici
CVE-2026-6734
Summary of CVE-2026-6734 : A vulnerability in undici’s Socks5ProxyAgent causes cross-origin request routing by reusing a single connection pool across multiple origins without verifying the pool origin. As a result, requests for origin B can be dispatched through the pool for origin A; credential...
CVE-2026-14643
undici contains a cache-interceptor vulnerability where optional whitespace around the = in qualified no-cache or private Cache-Control directives is not normalized. In affected releases (7.0.0–7.28.x and 8.0.0–8.8.x), the parser may drop the directive or store a quoted field name, causing a cach...
CVE-2026-6733
Undici’s HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes; when the client issues the next request on that socket, the injected r...
CVE-2026-9675
The CVE-2026-9675 issue affects the undici WebSocket client (new WebSocket(...)) where per-frame maxPayloadSize is enforced but the cumulative size of fragmented, uncompressed messages is not. A attacker-controlled WebSocket endpoint can stream many small fragments that pass per-frame validation ...
CVE-2026-9679
undici vulnerability CVE-2026-9679 affects the cookie parsing paths (parseSetCookie, parseCookie, getSetCookies). The cookie parser percent-decodes values (via qsUnescape), turning sequences like %0D%0A, %00, %3B, and %3D into literal bytes. RFC 6265 §5.4 does not require decoding and browsers do...
CVE-2026-9678
Undici (node) vulnerability CVE-2026-9678: in shared-cache mode, the cache interceptor may misclassify responses as cacheable when Cache-Control uses whitespace-padded private/no-cache directives (e.g., private=" authorization" or no-cache="\tauthorization"). The whitespace is preserved by the pa...
CVE-2026-84890
undici , the Node.js HTTP client, is vulnerable to a denial of service via unbounded decompression of compressed responses. The decompress interceptor processes response bodies based on the untrusted Content-Encoding header. Although the number of encoding layers is capped, the total decompressed...