RUSTSEC-2026-0553: Malformed quoted chunk extensions can end HTTP/1.1 request bodies early

Published Nov 16, 2026
·
Updated

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

1 affected componentFixes available
rust/actix-http>=0.0.0-0<3.21.3
3.21.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/actix-http to a version that resolves this vulnerability.

    Fixed in 3.21.3
  2. Upgrade

    Upgrade actix-http to a version that resolves this vulnerability.

    Fixed in 3.21.3

Event History

Nov 16, 2026
Advisory Published
via OSV·12:00 PM
Data Sourced
via OSV·12:00 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

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.

2

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.

3

Are proxy bypass, cache poisoning, or cross-user response mixing confirmed impacts?

No. These impacts were not demonstrated by the available reproduction.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203