RUSTSEC-2026-0554: Partial requests on keep-alive connections can bypass the request header timeout
Affected versions of actix-http apply the request header timeout only to the first request on an HTTP/1 connection. When data arrives for a later request, the dispatcher clears the idle keep-alive timer without starting a request header timer.
A remote client without authentication can complete one request, send one byte of a second request, and leave the connection open indefinitely without sending more data. The same problem occurs when a complete pipelined request is followed by a partial request in the same read. Repeating this can exhaust connection or file-descriptor limits and prevent new connections from being accepted. The effect depends on the server's resource limits and upstream connection controls.
Upgrade to actix-http 3.21.2 or later. The fix applies the configured request header timeout to later partial requests, including those left in the buffer after a complete pipelined request. Additional bytes do not renew the deadline. The timeout covers request headers, not upload bodies.
If an upgrade is not possible, disable HTTP keep-alive, for example with HttpServer::keepalive(KeepAlive::Disabled) in actix-web. Connection limits can reduce resource use but do not make stalled connections expire.