Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85216 – Authentication Bypass (LDAP/LinOTP) – MISP ≤ 2.5.45

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85216 is a critical authentication bypass vulnerability in MISP (Malware Information Sharing Platform), affecting the platform’s LDAP and LinOTP authentication plugins in versions up to and including 2.5.45. The flaw allows an attacker who knows a valid directory user’s email address to authenticate as that user by submitting an empty password, potentially gaining administrative access. The vulnerability carries a CVSS score of 9.5 (Critical).

Technical details

  • Root cause: the custom LDAP and LinOTP authentication components in MISP did not replicate the credential validation checks performed by CakePHP’s default form authentication, allowing empty or non-string password values to be passed through to the underlying authentication mechanisms.
  • Trigger condition: an LDAP server configured to accept unauthenticated ("anonymous") binds may return a success response when a valid distinguished name is submitted together with an empty password, letting the attacker impersonate that account without knowing its real password. The LinOTP authenticator was similarly affected by insufficient validation of submitted credential values.
  • Attack vector: network-based and unauthenticated; the attacker only needs to know or guess the email address of a valid directory-managed user.
  • Impact: full impersonation of existing MISP users, including administrative accounts, enabling unauthorized read/write access to threat-intelligence data, modification or deletion of events, and changes to platform configuration.

Affected software

  • MISP versions 0 through 2.5.45 (inclusive), when the LDAP and/or LinOTP authentication plugins are enabled.

Severity

  • CVSS v4.0 Base Score: 9.5 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate: Upgrade MISP to a release that includes the fix committed to the LdapAuth and LinOTPAuth components (commit 0ee058548), which rejects empty and non-string credential values before they reach the authentication backend. Apply the latest available MISP release and confirm the fix is present in your version.
  • If immediate patching is not possible: Disable or restrict the LDAP and LinOTP authentication plugins where feasible, and ensure the backing LDAP directory is configured to reject unauthenticated ("anonymous") bind requests, which removes the underlying condition the bypass relies on.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Set-cookie response header: MISP-
  • Raw response body: href="https://github.com/MISP/MISP"
  • Loaded script URL: /js/misp.js

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge