Critical severity · published Sep 14, 2026
CVE-2026-90961
MISP LdapAuth and LinOTPAuth Authentication Bypass via Empty or Non-String Credentials
9.3
CVSS
0.6%
EPSS
No
On KEV
Description
The LdapAuth and LinOTPAuth authentication plugins in MISP contain an authentication bypass vulnerability. Both LdapAuthenticate and LinOTPAuthenticate replace CakePHP's FormAuthenticate class but fail to replicate its _checkFields() input validation guard. As a result, the email and password fields extracted from the login request are passed to downstream authentication logic without verifying that they are non-empty strings. In the LDAP authenticator, an empty or null password is forwarded to ldap_bind(). Per RFC 4513 section 5.1.2, a bind request with a valid DN and an empty password constitutes an unauthenticated bind, which many LDAP directory servers accept as successful. An attacker who knows any valid user email address in the directory can therefore authenticate as that user without possessing a password. Additionally, non-string values (null, false, arrays) are either coerced to empty strings by ldap_bind(), raise TypeErrors, or are misinterpreted as find conditions in _findUser(), all of which can lead to unintended authentication outcomes. In the LinOTP authenticator, the same missing guard allows non-string credentials to be concatenated into the LinOTP verification request, and in the mixed-authentication branch an empty password is accepted against a stored hash of the empty string. A secondary issue in the LDAP authenticator is that newly created user accounts (auto-provisioned on first LDAP login) were assigned an empty password. Because the save path skips validation, the empty string is hashed and stored. If the user later ceases to be found in LDAP and the mixed-authentication fallback is used, the stored hash of the empty string verifies against an empty password, again permitting unauthenticated access. The vulnerability requires that the affected plugin (LdapAuth or LinOTPAuth) is enabled on the MISP instance and that the attacker knows at least one valid email address registered in the directory or MISP user store. No prior authentication is required. Successful exploitation grants the attacker the full privileges of the impersonated user, which may include administrative access to threat intelligence data. Version affected: ≤2.5.45
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 50% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MI
MISP · MISP
before 2.5.46 · source: vendor
Affected product
MI
MISP
MISP
More from MISP
10.0
CVE-2026-10611
OTP bypass via plugin-based LDAP authentication in MISP when LDAP mixed authentication is enabled
9.8
CVE-2026-85216
MISP LDAP and LinOTP Authentication Bypass via Empty or Invalid Credentials
9.6
CVE-2026-39962
LDAP injection in MISP ApacheAuthenticate when using a user-controlled Apache environment variable
9.4
CVE-2026-56422
MISP Core: Mass Assignment and Object Re-ownership via Unvalidated Request Fields
9.3
CVE-2026-103655
MISP TOTP Code Replay Allows Duplicate Authentication Within Validity Period