Advisory

RUSTSEC-2026-0552

Also known as: GHSA-9w4r-xc43-v236

Summary

Bare LF in chunked trailers can consume pipelined requests or stall body decoding

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-11-16 12:00 UTC
Modified
2026-11-17 10:15 UTC

Affected packages and fixes

actix-http

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 3.21.1 (semver)

Fixed versions

3.21.1

Fix

  • Fixed version 3.21.1
    cargo update -p actix-http --precise 3.21.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC BY 4.0

This record names its own licence, CC BY 4.0, which differs from the source's (CC0-1.0).

Sources & licences