RUSTSEC-2026-0446: Request smuggling through malformed chunked request trailers

Open
#3,681 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
53/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
security

Research direction

The issue reports an advisory for actix-http and says to upgrade to 3.20.2 or later, but it does not name a docs.rs file or specific change to make. Start by checking how docs.rs handles RustSec advisories and determine whether the advisory is already reflected; done means the reported vulnerability and patched version are accurately represented in the relevant docs.rs output.

Written by the indexing model from the issue text.

Description

Request smuggling through malformed chunked request trailers

Details
Package actix-http
Version 3.20.0
URL https://github.com/actix/actix-web/commit/feed12e9ec59b39abe90590bf48ae6399ed45b56
Date 2026-11-06
Patched versions >=3.20.2

The HTTP/1 chunked decoder accepts a bare line feed after the final chunk as
the start of a trailer instead of rejecting the malformed request.

When an upstream proxy reuses a connection and either pipelines the requests or
does not take steps to validate the chunked stream, the decoder can consume the
next request's headers as trailer data. It can then parse that request's body as
a new request. An attacker can use this difference in request parsing to bypass
access controls enforced by a proxy or web application firewall.

Upgrade to actix-http 3.20.2 or later.

See advisory page for additional details.

Dominant language
Rust
Stars
1.2k
Forks
235
Avg merge
11h 56m
Merged PRs (30d)
78

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/docs.rs

All issues in rust-lang/docs.rs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.