<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T15:50:48.879485+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-neo4j-2026-1524</id>
    <title>BIT-neo4j-2026-1524 — Auth misconfiguration when multiple providers enabled</title>
    <updated>2026-10-07T15:50:48.933933+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: neo4j</p>
<p>An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:</p>
<p>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.</p>
<p>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.</p>
<p>We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-neo4j-2026-1524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-275803</id>
    <title>EUVD-2026-275803</title>
    <updated>2026-10-07T15:50:48.934000+00:00</updated>
    <content>EUVD-2026-275803</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-275803"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-1524</id>
    <title>fkie_cve-2026-1524</title>
    <updated>2026-10-07T15:50:48.934017+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:</p>
<p>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.</p>
<p>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.</p>
<p>We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-1524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5pgp-mc2w-hjjx</id>
    <title>GHSA-5pgp-mc2w-hjjx</title>
    <updated>2026-10-07T15:50:48.934049+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:</p>
<p>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.</p>
<p>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.</p>
<p>We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5pgp-mc2w-hjjx"/>
  </entry>
</feed>
