In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization.
Unless you use mitmproxy to protect an HTTP/1 service, no action is required.
// patches
The vulnerability has been fixed in mitmproxy 8.0.0 and above.
// acknowledgements
We thank Zeyu Zhang (@zeyu2001) for responsibly disclosing this vulnerability to the mitmproxy team.
// timeline
2022-03-15: Received initial report.
2022-03-15: Verified report and confirmed receipt.
2022-03-16: Shared patch with researcher.
2022-03-16: Received confirmation that patch is working.
2022-03-19: Published patched release and advisory.
// cvss v3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Checked 2026-11-06 at 22:10 UTC. The most recent advisory here was published 2026-04-14. Updated continuously from NVD, GHSA, OSV and CNA feeds.