RUSTSEC-2026-0554
Partial requests on keep-alive connections can bypass the request header timeout
Overview
Description
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::keep_alive(KeepAlive::Disabled) in actix-web. Connection limits
can reduce resource use but do not make stalled connections expire.
Source: OX vulnerability database
Severity
MEDIUM
No CVSS vector in the source. Severity comes from the advisory.
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Cargo (Rust) | actix-http | >=0.0.0-0, <3.21.2 | 3.21.2 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.