RUSTSEC-2026-0553: Malformed quoted chunk extensions can end HTTP/1.1 request bodies early
Affected versions of actix-http do not track quoted strings when parsing HTTP/1.1 chunk extensions. A carriage return inside a quoted extension value is treated as the end of the chunk-size line, even if the closing quote is missing. For example, 0;x="\r\n\r\n is accepted as the end of a chunked body, and a following pipelined request is dispatched on the same connection.
A remote client can trigger this without authentication. CR and LF are invalid inside HTTP quoted strings, including after a backslash; they must be rejected rather than interpreted as framing or accepted as quoted data.
Request smuggling requires an upstream intermediary that forwards the malformed input while using a different request boundary. Dispatching two requests on the sender's own connection does not by itself demonstrate an authorization bypass or an effect on another user. Proxy bypass, cache poisoning, and cross-user response mixing were not demonstrated by the reproduction.
Upgrade to actix-http 3.21.3 or later. The fix preserves quote and escape state across reads and rejects invalid control bytes inside quoted strings and quoted pairs before consuming the following body or request bytes.
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.3 - Upgrade
Upgrade
actix-httpto a version that resolves this vulnerability.Fixed in 3.21.3
Event History
Frequently Asked Questions
What conditions are required for this to become a request-smuggling issue?
An upstream intermediary must forward the malformed chunked request while determining request boundaries differently from the affected actix-http server. A client sending two requests on its own connection is not, by itself, evidence of an authorization bypass or impact on another user.
Can an unauthenticated remote attacker trigger the parsing flaw?
Yes. A remote client can send a malformed HTTP/1.1 chunk extension containing a carriage return in an unterminated quoted value without authentication.
Are proxy bypass, cache poisoning, or cross-user response mixing confirmed impacts?
No. These impacts were not demonstrated by the available reproduction.
What should be upgraded to remediate the issue?
Upgrade actix-http to version 3.21.3 or later. The fix retains quote and escape parsing state across reads and rejects invalid control bytes in quoted strings and quoted pairs before subsequent body or request bytes are consumed.