<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 14:09:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-85216 — MISP LDAP and LinOTP Authentication Bypass via Empty or Invalid Credentials</title>
      <link>https://db.gcve.eu/vuln/cve-2026-85216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP contains an authentication bypass vulnerability in its LDAP and LinOTP authentication components due to insufficient validation of user-supplied credentials.&lt;/p&gt;
&lt;p&gt;The custom LdapAuthenticate and LinOTPAuthenticate components replace CakePHP&amp;#39;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.&lt;/p&gt;
&lt;p&gt;In the LDAP authentication path, an attacker able to identify a valid directory user&amp;#39;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&amp;#39;s password.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Successful exploitati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP contains an authentication bypass vulnerability in its LDAP and LinOTP authentication components due to insufficient validation of user-supplied credentials.&lt;/p&gt;
&lt;p&gt;The custom LdapAuthenticate and LinOTPAuthenticate components replace CakePHP&amp;#39;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.&lt;/p&gt;
&lt;p&gt;In the LDAP authentication path, an attacker able to identify a valid directory user&amp;#39;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&amp;#39;s password.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Successful exploitati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-85216</guid>
    </item>
  </channel>
</rss>
