Skip to content
Fencer Intel
no cvss —

GHSA-54pm-2wm5-hpmg json

Partial requests on keep-alive connections can bypass the request header timeout

published yesterday modified 18h ago also RUSTSEC-2026-0554

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io actix-http 3.21.2

Is GHSA-54pm-2wm5-hpmg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io actix-http
>=0.0.0-0, <3.21.2
3.21.2

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.