Misp-Project Misp
CVE-2026-85216
MISP contains an authentication bypass vulnerability in its LDAP and LinOTP authentication components due to insufficient validation of user-supplied credentials. The custom LdapAuthenticate and LinOTPAuthenticate components replace CakePHP's FormAuthenticate implementation but did not replicate its credential validation checks. As a result, empty or non-string values could reach the underlying authentication mechanisms. In the LDAP authentication path, an attacker able to identify a valid directory user's email address could submit an empty password. The empty credential could be passed to ldap_bind(), where an LDAP server accepting unauthenticated binds may return a successful result for a valid distinguished name combined with an empty password. MISP could consequently treat the attacker as the corresponding authenticated directory user without verification of the user's password. The issue also affected the LinOTP authentication component. Invalid credential types were not rejected before being processed, and when mixed authentication was enabled, an empty password could be checked against a locally stored MISP password hash. LDAP-provisioned MISP accounts could additionally be created with an empty local password because account creation skipped normal validation, resulting in a hash corresponding to an empty password. This could permit authentication through the local fallback mechanism when such an account was no longer resolved through LDAP. Successful exploitation could allow a remote unauthenticated attacker to impersonate an existing MISP user. If the targeted account has administrative or other privileged permissions, the attacker could gain corresponding access to sensitive threat-intelligence data, modify or delete information, alter configuration, or perform other privileged operations. The patch resolves the vulnerability by requiring authentication identifiers and passwords to be valid strings, rejecting empty passwords where they are not explicitly
What this means for your business
- It affects Misp-Project Misp. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.9% chance of attack attempts being seen in the next 30 days, ranking above 57% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Misp-Project Misp, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Fastnexa security experts
Not sure if your company is exposed to CVE-2026-85216?
Tell us where you run Misp-Project Misp and a Fastnexa penetration tester will check whether this flaw, or others like it, can be used against your websites, apps and network.
The full test is free for our first 10 founding clients until 31 December 2026. See the offer
Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →
Scoring
- CVSS
- 9.8 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- CVSS v4
- 9.5
- Weakness
- CWE-521
- Assigned by
- 5a6e4751-2f3f-4070-9419-94fb35b644e8
Dates
- Published
- 2026-09-03
- Last modified
- 2026-09-10
- Sources
- NVD
Affected products
- Misp-Project Misp- 2.5.46
As listed in the NVD configuration data. Not a statement about your estate.