CVE-2026-10611: OTP bypass via plugin-based LDAP authentication in MISP when LDAP mixed authentication is enabled
An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement. In deployments configured with LdapAuth.mixedAuth=true and Security.requireotp=true, users authenticated through an authentication plugin, such as LDAP, may have their authenticated session established during the application beforeFilter phase before the normal login flow enforces the OTP challenge.
As a result, an attacker with valid primary authentication credentials could bypass the required OTP step by authenticating through the plugin-backed login flow and then directly accessing another application URL instead of completing the OTP verification page. This allows access to the application as the affected user without providing a valid TOTP, HOTP, or email OTP code.
The issue affects configurations where plugin-based authentication is enabled and OTP is expected to be mandatory. The fix ensures that OTP requirements are checked immediately after plugin authentication and before the user session is established, redirecting users to the appropriate OTP challenge when required.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-10611?
The severity of CVE-2026-10611 is high with a CVSS score of 8.2.
How do I fix CVE-2026-10611?
To fix CVE-2026-10611, disable mixed authentication for LDAP or ensure that OTP enforcement is not relied upon for authentication.
What does CVE-2026-10611 affect?
CVE-2026-10611 affects organizations using the MISP Project with LDAP mixed authentication enabled and OTP enforcement.
What are the risks of CVE-2026-10611?
The risks of CVE-2026-10611 include potential unauthorized access due to the authentication bypass vulnerability.
When was CVE-2026-10611 published?
CVE-2026-10611 was published on June 2, 2026.