RUSTSEC-2026-0552: Bare LF in chunked trailers can consume pipelined requests or stall body decoding
Affected versions of actix-http skip a bare line feed (LF) inside an HTTP/1.1 chunked trailer instead of rejecting the invalid line ending. Trailer lines must end with a carriage return and line feed (CRLF).
For example, after 0\r\nX\n, the parser continues reading trailer data. If a request follows on the same connection, its head can be consumed as part of the trailer, so that request is never dispatched. If no more bytes arrive, body decoding waits for more input instead of reporting an error. A remote client can trigger these effects without authentication.
Request smuggling additionally requires an HTTP intermediary that forwards the malformed body but uses a different request boundary. The tested HTTP intermediaries either rejected the input or consumed and normalized it before forwarding. Proxy access-control bypass, cache poisoning, and effects on other users were not demonstrated.
Upgrade to actix-http 3.21.1 or later. The fix rejects bare LF and invalid control bytes in trailers before consuming the following request, while preserving partial reads and valid CRLF-terminated trailers.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rust/actix-httpto a version that resolves this vulnerability.Fixed in 3.21.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.21.1