HTTP/2 request bodies made of 1-byte DATA frames amplify memory use in Bandit

SETTINGS and stream-0 WINDOW_UPDATE frames trigger quadratic work over blocked streams in Bandit

Client-chosen HPACK encoder table size is applied uncapped, growing per-connection state with every response in Bandit

HTTP/2 cookie crumb join expands a small HPACK header block into an unbounded allocation in Bandit

HTTP/1.1 chunked request bodies made of 1-byte chunks amplify memory use in Bandit

Quadratic bignum parsing of Content-Length and Host port values in Bandit

WebSocket 1-byte continuation frames bypass `max_fragmented_message_size` in Bandit

HTTP/2 WINDOW_UPDATE and SETTINGS frames reset the request body read timeout in Bandit

HTTP/2 inbound flow control is not enforced, letting a client queue unbounded DATA in stream processes in Bandit

HTTP/2 blocked-send deadlines reset on every WINDOW_UPDATE, letting a trickle pin stream processes indefinitely in Bandit

HTTP/2 connection-window starvation pins Plug processes indefinitely in Bandit

Quadratic CPU blow-up reassembling fragmented WebSocket messages in Bandit

WebSocket fragmented message reassembly unbounded in bandit

HTTP/2 StreamError recovery rolls back connection state and bypasses per-connection limits in Bandit

WebSocket permessage-deflate inflate has no output-size cap in bandit

HTTP/1 chunked decoder infinite loop on requests with trailer fields in bandit

HTTP/1 chunked body reader ignores length cap in bandit