Cyber Resilience

CVE-2026-40606

Mitmproxy ≤ 12.2.2

Published
21 April 2026
Modified
24 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0017 6th percentile
Risk Priority 37 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-40606 is a medium-severity LDAP Injection (CWE-90) vulnerability in Mitmproxy Mitmproxy. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying…

more

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. The vulnerability has been fixed in mitmproxy 12.2.2 and above.

CWE(s)
CWE-90

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-29138Shared CWE-90
CVE-2026-40459Shared CWE-90
CVE-2026-13696Shared CWE-90
CVE-2025-27631Shared CWE-90
CVE-2026-0636Shared CWE-90
CVE-2026-44063Shared CWE-90
CVE-2026-49268Shared CWE-90
CVE-2025-52575Shared CWE-90
CVE-2024-33868Shared CWE-90
CVE-2025-48208Shared CWE-90

Affected Assets

mitmproxy
mitmproxy
≤ 12.2.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

A.8.27 Secure system architecture and engineering principles none match
mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

References