CVE-2026-40606: mitmproxy has an LDAP Injection
Impact In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying the LDAP server. This allows a malicious client to bypass authentication. Only mitmproxy instances using the proxyauth option with LDAP are affected. This option is not enabled by default. Patches The vulnerability has been fixed in mitmproxy 12.2.2 and above.
Published Apr 14, 2026 · Updated Jun 6, 2026
Affected packages
mitmproxy
- Ecosystem
- PyPI
- Affected
- <= 12.2.1
- Fixed in
- 12.2.2
- Check
pip show mitmproxy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying the LDAP server. This allows a malicious client to bypass authentication.
Only mitmproxy instances using the proxyauth option with LDAP are affected. This option is not enabled by default.
Patches
The vulnerability has been fixed in mitmproxy 12.2.2 and above.
Acknowledgements
We thank Yue (Knox) Liu (@yueyueL) for responsibly disclosing this vulnerability to the mitmproxy team.
Timeline
- 2025-12-08: Received initial report.
- 2025-12-09: Verified report and confirmed receipt.
- 2026-01-02: Informed researcher that patch will be part of the next regular patch release.
- 2026-04-12: Published patch release and advisory.
Credited to yueyueL, mhils.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
