Vulnerability Database · PyPI · mitmproxy · Version
mitmproxy 11.1.2
11.1.2 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 3 Low 0 Unrated 0
-
Released 06 Feb 2025
Licence non-standard
Also known from other sources 3
Newer releases 87
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
mitmproxy 11.1.2 vulnerabilities
3 vulnerabilities cover mitmproxy 11.1.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Moderate Vulnerability in mitmproxy: HTTP/2 Header Validation Flaw | 6.9 medium | 12.1.2 | 25 Aug 2025 |
| CVE-2026-40606: mitmproxy LDAP Authentication Bypass Vulnerability | 4.8 medium | 12.2.2 | 21 Apr 2026 |
| LDAP Injection Vulnerability in mitmproxy: Bypass Authentication Risk | 4.8 medium | 12.2.2 | 14 Apr 2026 |
Looking for another version, or everything Vulert holds for mitmproxy?
Questions
About mitmproxy 11.1.2
Is mitmproxy 11.1.2 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover mitmproxy 11.1.2: 0 critical, 0 high, 3 medium and 0 low. Each entry above names the fixed version to move to.
Is 11.1.2 the latest release of mitmproxy?
No. 11.1.2 was published 06 Feb 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor mitmproxy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mitmproxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.