<?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>Wed, 07 Oct 2026 08:40:51 +0000</lastBuildDate>
    <item>
      <title>BIT-neo4j-2026-1524 — Auth misconfiguration when multiple providers enabled</title>
      <link>https://cve.radiocsirt.org/vuln/bit-neo4j-2026-1524</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: neo4j&lt;/p&gt;
&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: neo4j&lt;/p&gt;
&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-neo4j-2026-1524</guid>
    </item>
    <item>
      <title>EUVD-2026-275803</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275803</link>
      <description>EUVD-2026-275803</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275803</guid>
    </item>
    <item>
      <title>fkie_cve-2026-1524</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-1524</link>
      <description>&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-1524</guid>
    </item>
    <item>
      <title>GHSA-5pgp-mc2w-hjjx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5pgp-mc2w-hjjx</link>
      <description>&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:&lt;/p&gt;
&lt;p&gt;If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.&lt;/p&gt;
&lt;p&gt;When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.&lt;/p&gt;
&lt;p&gt;We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5pgp-mc2w-hjjx</guid>
    </item>
  </channel>
</rss>
