{"id":"CVE-2022-24766","aliases":["DEBIAN-CVE-2022-24766","EUVD-2022-0156","GHSA-gcx2-gvj7-pxv3","PYSEC-2022-170","UBUNTU-CVE-2022-24766","openSUSE-SU-2024:11956-1","openSUSE-SU-2025:14762-1"],"status":"published","title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","description":"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.","severity":{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.01633,"percentile":0.76431,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-444"],"published":"2022-03-21T18:50:10Z","modified":"2026-11-03T08:03:51Z","fixes":[{"ecosystem":"PyPI","package":"mitmproxy","fixed_in":["8.0.0"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:12","package":"mitmproxy","fixed_in":["8.1.1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"mitmproxy","fixed_in":["8.1.1-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.1.1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.1.1-1"}]}],"versions":["0.10-1","0.10-2","0.10.1-1","0.10.1-2","0.11.3-1","0.11.3-2","0.11.3-3","0.12.1-1","0.12.1-2","0.13-1","0.15-1","0.15-2","0.18.1-1","0.18.1-2","0.18.2-1","0.18.2-2","0.18.2-3","0.18.2-4","0.18.2-5","0.18.2-6","0.6-1","0.6-2","0.6-3","0.7-1","0.8-1","0.8-2","0.9.1-1","0.9.1-2","0.9.2-1","0.9.2-2","2.0.2-1","2.0.2-2","2.0.2-3","2.0.2-4","3.0.3-1","3.0.4-1","4.0.4-1","4.0.4-2","4.0.4-3","4.0.4-4","4.0.4-5","4.0.4-6","4.0.4-6.1","5.1.1-1","5.1.1-2","5.3.0-1","5.3.0-2","5.3.0-3","6.0.2-1","6.0.2-2"]},{"source":"osv","ecosystem":"PyPI","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.0"}]}],"versions":["0.10","0.10.1","0.11","0.11.1","0.11.2","0.11.3","0.12.0","0.12.1","0.13","0.14.0","0.15","0.16","0.17","0.18.1","0.18.2","0.18.3","0.8","0.8.1","0.9","0.9.1","0.9.2","1.0.0","1.0.1","1.0.2","2.0.0","2.0.1","2.0.2","3.0.0","3.0.1","3.0.2","3.0.3","3.0.4","4.0.0","4.0.1","4.0.3","4.0.4","5.0.0","5.0.1","5.1.0","5.1.1","5.2","5.3.0","6.0.0","6.0.1","6.0.2","7.0.0","7.0.1","7.0.2","7.0.3","7.0.4"]},{"source":"osv","ecosystem":"PyPI","package":"mitmproxy","ranges":[{"type":"GIT","events":[{"introduced":"0"},{"fixed":"b06fb6d157087d526bd02e7aadbe37c56865c71b"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.0"}]}],"versions":["0.10","0.10.1","0.11","0.11.1","0.11.2","0.11.3","0.12.0","0.12.1","0.13","0.14.0","0.15","0.16","0.17","0.18.1","0.18.2","0.18.3","0.8","0.8.1","0.9","0.9.1","0.9.2","1.0.0","1.0.1","1.0.2","2.0.0","2.0.1","2.0.2","3.0.0","3.0.1","3.0.2","3.0.3","3.0.4","4.0.0","4.0.1","4.0.3","4.0.4","5.0.0","5.0.1","5.1.0","5.1.1","5.2","5.3.0","6.0.0","6.0.1","6.0.2","7.0.0","7.0.1","7.0.2","7.0.3","7.0.4"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.11.3-3","0.12.1-2","0.13-1","0.15-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.2-2","2.0.2-3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.0.4-6","4.0.4-6.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.2-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.1.1-2"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.1.1-2","8.1.1-3"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.1.1-4"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.1.1-3","8.1.1-4"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-mitmproxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.2-1.1"}]}],"bundled":3}],"products":[{"vendor":"mitmproxy","product":"mitmproxy"}],"references":[{"url":"https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web","report"]},{"url":"https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","web","report"]},{"url":"https://mitmproxy.org/posts/releases/mitmproxy8/","tags":["x_refsource_MISC","x_transferred","Release Notes","Vendor Advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-24766","tags":["advisory"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/mitmproxy/PYSEC-2022-170.yaml","tags":["web"]},{"url":"https://mitmproxy.org/posts/releases/mitmproxy8","tags":["web"]},{"url":"https://github.com/advisories/GHSA-gcx2-gvj7-pxv3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/24xxx/CVE-2022-24766.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-24766","tags":["advisory"]},{"url":"https://github.com/mitmproxy/mitmproxy","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2022-24766","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-24766","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2022-24766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23217","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2022-24766","title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","description":"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.","status":"published","published":"2022-03-21T18:50:10Z","modified":"2025-04-23T18:45:30.363Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"cna"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:34:34.576287Z"}],"euvd":[{"id":"EUVD-2022-0156","description":"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.","status":"published","published":"2022-03-21T18:50:10Z","modified":"2025-04-23T18:45:30Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T20:52:07.950001Z"}],"ghsa":[{"id":"GHSA-gcx2-gvj7-pxv3","title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","description":"### Impact\n\nIn mitmproxy 7.0.4 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/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.\n\nUnless you use mitmproxy to protect an HTTP/1 service, no action is required.\n\n\n### Patches\n\nThe vulnerability has been fixed in mitmproxy 8.0.0 and above.\n\n\n### Acknowledgements\n\nWe thank Zeyu Zhang (@zeyu2001) for responsibly disclosing this vulnerability to the mitmproxy team.\n\n\n### Timeline\n\n- **2022-03-15**: Received initial report.\n- **2022-03-15**: Verified report and confirmed receipt.\n- **2022-03-16**: Shared patch with researcher.\n- **2022-03-16**: Received confirmation that patch is working.\n- **2022-03-19**: Published patched release and advisory.","status":"published","published":"2022-03-22T19:22:59Z","modified":"2024-10-01T19:30:28Z","cvss":[{"version":"4.0","score":9.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"critical"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:38:07.852618Z"}],"nvd":[{"id":"CVE-2022-24766","description":"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.","status":"published","published":"2022-03-21T19:15:11.613Z","modified":"2026-06-17T04:32:28.263Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"secondary"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"},{"version":"2.0","score":7.5,"vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","level":"high","assessor":"primary"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:07:14.24948Z"}],"osv":[{"id":"CVE-2022-24766","title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","description":"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.","status":"published","published":"2022-03-21T18:50:10Z","modified":"2026-10-28T02:30:44.212367251Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T15:44:24.428403Z"},{"id":"DEBIAN-CVE-2022-24766","description":"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.","status":"published","published":"2022-03-21T19:15:11.613Z","modified":"2026-11-03T08:03:51.248957798Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-03T08:23:57.167851Z"},{"id":"GHSA-gcx2-gvj7-pxv3","title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","description":"### Impact\n\nIn mitmproxy 7.0.4 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/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.\n\nUnless you use mitmproxy to protect an HTTP/1 service, no action is required.\n\n\n### Patches\n\nThe vulnerability has been fixed in mitmproxy 8.0.0 and above.\n\n\n### Acknowledgements\n\nWe thank Zeyu Zhang (@zeyu2001) for responsibly disclosing this vulnerability to the mitmproxy team.\n\n\n### Timeline\n\n- **2022-03-15**: Received initial report.\n- **2022-03-15**: Verified report and confirmed receipt.\n- **2022-03-16**: Shared patch with researcher.\n- **2022-03-16**: Received confirmation that patch is working.\n- **2022-03-19**: Published patched release and advisory.","status":"published","published":"2022-03-22T19:22:59Z","modified":"2025-02-22T05:12:43.323943Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"},{"version":"4.0","score":9.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T15:46:47.822182Z"},{"id":"UBUNTU-CVE-2022-24766","description":"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.","status":"published","published":"2022-03-21T19:15:00Z","modified":"2026-10-17T12:56:20.932393304Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T16:53:53.13624Z"},{"id":"openSUSE-SU-2024:11956-1","title":"python310-mitmproxy-8.0.0-1.1 on GA media","description":"These are all security issues fixed in the python310-mitmproxy-8.0.0-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:19:12.432343Z","updated_at":"2026-11-02T16:58:35.485255Z"},{"id":"openSUSE-SU-2025:14762-1","title":"python312-mitmproxy-11.1.2-1.1 on GA media","description":"These are all security issues fixed in the python312-mitmproxy-11.1.2-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-02-10T00:00:00Z","modified":"2026-02-04T03:22:25.216444Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"PYSEC-2022-170","description":"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.","status":"published","published":"2022-03-21T19:15:00Z","modified":"2023-11-08T04:08:35.674152Z","updated_at":"2026-11-02T15:52:53.449407Z"}]}}