CVE-2026-40606: mitmproxy · LDAP Injection
Affects mitmproxySource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 12.2.2 when convenient.
Data as of 12 Nov 2026, 01:33 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.8 |
|---|
- Patch
- Available – fixed in 12.2.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade mitmproxy to 12.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mitmproxy mitmproxy | Affected
| Fixed in
|
AI-suggested
Upgrade mitmproxy to version 12.2.2 or later, where this LDAP injection vulnerability is fixed. If upgrading immediately is not possible, disable the proxyauth option with LDAP to avoid exposure, as this option is not enabled by default.
Description
CVE-2026-40606 is an LDAP injection vulnerability in mitmproxy versions 12.2.1 and below. The issue occurs because the builtin LDAP proxy authentication does not properly sanitize usernames when querying the LDAP server, allowing a malicious client to bypass authentication. This vulnerability affects only mitmproxy instances that have the proxyauth option enabled with LDAP, which is not enabled by default. The vulnerability is fixed in mitmproxy version 12.2.2 and later.