CVE-2021-39214: Lacking Protection against HTTP Request Smuggling in mitmproxy
Noroxi assessment
Priority: Monitor (action score 39/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: mitmproxy (Alpine:v3.21) 7.0.3-r0; mitmproxy (Debian:12) 8.1.1-1; python-mitmproxy (openSUSE:Leap 15.4) 3.0.4-bp154.2.3.1.
Low priority for now. Upgrade to mitmproxy (Alpine:v3.21) 7.0.3-r0; mitmproxy (Debian:12) 8.1.1-1; python-mitmproxy (openSUSE:Leap 15.4) 3.0.4-bp154.2.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.2 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 a smuggled request is still captured as part of another request's body, 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 one uses mitmproxy to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 7.0.3 and above.
- Published
- Sep 16, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 64th percentile
- CWE
- CWE-444
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 8.1
- 1.7 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mitmproxy | mitmproxy | cpe:2.3:a:mitmproxy:mitmproxy |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
mitmproxy mitmproxy
- < 7.0.3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mitmproxy mitmproxyup to 7.0.2 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | mitmproxy | before 7.0.3-r0 | 7.0.3-r0 |
| Debian:12 | mitmproxy | before 8.1.1-1 | 8.1.1-1 |
| openSUSE:Leap 15.4 | python-mitmproxy | before 3.0.4-bp154.2.3.1 | 3.0.4-bp154.2.3.1 |
| openSUSE:Leap 15.5 | python-mitmproxy | before 3.0.4-bp155.3.3.1 | 3.0.4-bp155.3.3.1 |
| PyPI | mitmproxy | before 7.0.3 | 7.0.3 |
| SUSE:Package Hub 15 SP4 | python-mitmproxy | before 3.0.4-bp154.2.3.1 | 3.0.4-bp154.2.3.1 |
| SUSE:Package Hub 15 SP5 | python-mitmproxy | before 3.0.4-bp155.3.3.1 | 3.0.4-bp155.3.3.1 |
Same product
mitmproxy: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-24766Insufficient Protection against HTTP Request Smuggling in mitmproxy39Monitor
- CVE-2018-14505mitmweb in mitmproxy v4.0.3 allows DNS Rebinding attacks, related to tools/web/app.py.36Monitor
- CVE-2025-23217Mitmweb API Authentication Bypass Using Proxy Server32Monitor
Published before and after this one in the same product
- Later →CVE-2026-40606Apr 21, 2026 · ProxyAuth Addon LDAP Injection in mitmproxy19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:mitmproxy | 7.0.3-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:mitmproxy | 8.1.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:python-mitmproxy | 3.0.4-bp154.2.3.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| PyPI:mitmproxy | 7.0.3 | Package registry (OSV) |
| suse:python-mitmproxy | 3.0.4-bp154.2.3.1 · SUSE:Package Hub 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2026-10-08 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+1848 d
- TodayNov 16, 2026+1887 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- Exploit maturitynone → poc
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.