# CVE-2022-24766: Insufficient Protection against HTTP Request Smuggling in mitmproxy

Source: https://junglewise.ai/threats/cve-2022-24766-insufficient-protection-against-http-request-smuggling-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-03-21  
License: CC BY 4.0 with a link back

CVE-2022-24766 · Severity: low · CVSS 3.1 · Published 2022-03-21

mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. 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 mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.

Technologies: [mitmproxy (PyPI)](https://junglewise.ai/threats/technologies/mitmproxy). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2022-24766 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-24766 being exploited in the wild.

**How severe is CVE-2022-24766?** Low severity, with a CVSS score of 3.1, published 21 March 2022.

**Which products and versions are affected?** mitmproxy (PyPI) ECOSYSTEM:introduced=0,fixed=8.0.0, GIT:introduced=0,fixed=b06fb6d157087d526bd02e7aadbe37c56865c71b|ECOSYSTEM:introduced=0,fixed=8.0.0.

**Is there a fix for CVE-2022-24766?** Yes. mitmproxy (PyPI): upgrade to 8.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2022-24766?** Check whether you run mitmproxy (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- mitmproxy (PyPI): upgrade to 8.0.0 or later

  ```sh
  pip install "mitmproxy>=8.0.0"
  ```


## Affected products

- mitmproxy (PyPI) ECOSYSTEM:introduced=0,fixed=8.0.0, GIT:introduced=0,fixed=b06fb6d157087d526bd02e7aadbe37c56865c71b|ECOSYSTEM:introduced=0,fixed=8.0.0

## Identifiers

- CVE-2022-24766
- GHSA-gcx2-gvj7-pxv3
- PYSEC-2022-170

## Related threats

- [PYSEC-2026-1630 - Mitmweb API Authentication Bypass Using Proxy Server](https://junglewise.ai/threats/cve-2025-23217-mitmweb-api-authentication-bypass-using-proxy-server)
- [mitmproxy LDAP injection in LDAP proxy authentication](https://junglewise.ai/threats/cve-2026-40606-mitmproxy-ldap-injection-in-ldap-proxy-authentication)
- [mitmproxy binaries embed a vulnerable python-hyper/h2 dependency](https://junglewise.ai/threats/mitmproxy-binaries-embed-a-vulnerable-python-hyper-h2-dependency-e14cde4e)
- [mitmproxy HTTP request smuggling](https://junglewise.ai/threats/cve-2021-39214-mitmproxy-http-request-smuggling)
- [PYSEC-2018-56 - mitmweb in mitmproxy v4.0.3 allows DNS Rebinding attacks, related to tools/web/app.py.](https://junglewise.ai/threats/cve-2018-14505-mitmweb-in-mitmproxy-allows-dns-rebinding-attacks)