<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 19:06:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-319037</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319037</link>
      <description>EUVD-2026-319037</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319037</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44671</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44671</link>
      <description>&lt;p&gt;ZITADEL is an open source identity management platform. From 2.71.11 to before 3.4.10 and 4.15.0, a vulnerability was discovered in Zitadel&amp;#39;s LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process. While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as *, (, )) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory. This vulnerability is fixed in 3.4.10 and 4.15.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ZITADEL is an open source identity management platform. From 2.71.11 to before 3.4.10 and 4.15.0, a vulnerability was discovered in Zitadel&amp;#39;s LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process. While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as *, (, )) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory. This vulnerability is fixed in 3.4.10 and 4.15.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44671</guid>
    </item>
    <item>
      <title>GHSA-rxvx-hhpj-q6px — ZITADEL has LDAP Filter Injection in Login Flow</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rxvx-hhpj-q6px</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Zitadel&amp;#39;s LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as `*`, `(`, `)`) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory.&lt;/p&gt;
&lt;p&gt;Note that an authentication bypass is not possible.&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;Systems integrating LDAP as IdPs and running one of the following versions are affected:&lt;/p&gt;
&lt;p&gt;- **4.x**: `4.0.0` through `4.14.0` (including RC versions)
- **3.x**: `3.1.0` through `3.4.9`
- **2.x**: `2.71.11` through `2.71.19`&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address, resp. phone number itself.&lt;/p&gt;
&lt;p&gt;- **4.x**: Upgrade to &amp;gt;=[4.15.0](https://github.com/zitadel/zitadel/releases/tag/v4.15.0)
- **3.x**: Update to &amp;gt;=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.4.10)
- **2.x**: Update to &amp;gt;=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.4.10…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Zitadel&amp;#39;s LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as `*`, `(`, `)`) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory.&lt;/p&gt;
&lt;p&gt;Note that an authentication bypass is not possible.&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;Systems integrating LDAP as IdPs and running one of the following versions are affected:&lt;/p&gt;
&lt;p&gt;- **4.x**: `4.0.0` through `4.14.0` (including RC versions)
- **3.x**: `3.1.0` through `3.4.9`
- **2.x**: `2.71.11` through `2.71.19`&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address, resp. phone number itself.&lt;/p&gt;
&lt;p&gt;- **4.x**: Upgrade to &amp;gt;=[4.15.0](https://github.com/zitadel/zitadel/releases/tag/v4.15.0)
- **3.x**: Update to &amp;gt;=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.4.10)
- **2.x**: Update to &amp;gt;=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.4.10…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rxvx-hhpj-q6px</guid>
    </item>
  </channel>
</rss>
