<?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>Sat, 03 Oct 2026 06:43:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-261500</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-261500</link>
      <description>EUVD-2026-261500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-261500</guid>
    </item>
    <item>
      <title>fkie_cve-2023-6236</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-6236</link>
      <description>&lt;p&gt;A flaw was found in Red Hat Enterprise Application Platform 8. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new &amp;#34;provider-url&amp;#34; option in addition to the &amp;#34;realm&amp;#34; option.&#13;
&#13;
EAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found in Red Hat Enterprise Application Platform 8. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new &amp;#34;provider-url&amp;#34; option in addition to the &amp;#34;realm&amp;#34; option.&#13;
&#13;
EAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-6236</guid>
    </item>
    <item>
      <title>GHSA-jpmx-996v-48fm — WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jpmx-996v-48fm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.wildfly.security:wildfly-elytron-http-oidc&lt;/p&gt;
&lt;p&gt;A flaw was found in JBoss EAP. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new &amp;#34;provider-url&amp;#34; option in addition to the &amp;#34;realm&amp;#34; option.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.wildfly.security:wildfly-elytron-http-oidc&lt;/p&gt;
&lt;p&gt;A flaw was found in JBoss EAP. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new &amp;#34;provider-url&amp;#34; option in addition to the &amp;#34;realm&amp;#34; option.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jpmx-996v-48fm</guid>
    </item>
    <item>
      <title>gsd-2023-6236</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-6236</link>
      <description>gsd-2023-6236</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-6236</guid>
    </item>
    <item>
      <title>RHSA-2024:3580 — Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 8.0.2 Security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3580</link>
      <description>&lt;p&gt;eap-galleon: custom provisioning creates unsecured http-invoker EAP: OIDC app attempting to access the second tenant, the user should be prompted to log jberet: jberet-core logging database credentials EAP: wildfly-elytron has a SSRF security issue&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;eap-galleon: custom provisioning creates unsecured http-invoker EAP: OIDC app attempting to access the second tenant, the user should be prompted to log jberet: jberet-core logging database credentials EAP: wildfly-elytron has a SSRF security issue&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3580</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1286 — Red Hat JBoss Enterprise Application Platform: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1286</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat JBoss Enterprise Application Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen und Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat JBoss Enterprise Application Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen und Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1286</guid>
    </item>
  </channel>
</rss>
