<?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>Sun, 04 Oct 2026 11:28:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-237958</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-237958</link>
      <description>EUVD-2026-237958</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-237958</guid>
    </item>
    <item>
      <title>fkie_cve-2025-46815</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-46815</link>
      <description>&lt;p&gt;The identity infrastructure software ZITADEL offers developers the ability to manage user sessions using the Session API. This API enables the use of IdPs for authentication, known as idp intents. Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session. However, prior to versions 3.0.0, 2.71.9, and 2.70.10, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user. It&amp;#39;s important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API. Versions 3.0.0, 2.71.9, and 2.70.10 contain a fix for the issue. No known workarounds other than upgrading are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The identity infrastructure software ZITADEL offers developers the ability to manage user sessions using the Session API. This API enables the use of IdPs for authentication, known as idp intents. Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session. However, prior to versions 3.0.0, 2.71.9, and 2.70.10, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user. It&amp;#39;s important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API. Versions 3.0.0, 2.71.9, and 2.70.10 contain a fix for the issue. No known workarounds other than upgrading are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-46815</guid>
    </item>
    <item>
      <title>GHSA-g4r8-mp7g-85fq — ZITADEL Allows IdP Intent Token Reuse</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g4r8-mp7g-85fq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zitadel/zitadel&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;ZITADEL offers developers the ability to manage user sessions using the [Session API](https://zitadel.com/docs/category/apis/resources/session_service_v2/session-service). This API enables the use of IdPs for authentication, known as idp intents.&lt;/p&gt;
&lt;p&gt;Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session.&lt;/p&gt;
&lt;p&gt;However, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user.&lt;/p&gt;
&lt;p&gt;It’s important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;3.x versions are fixed on &amp;gt;=[3.0.0](https://github.com/zitadel/zitadel/releases/tag/v3.0.0)
2.71.x versions are fixed on &amp;gt;=[2.71.9](https://github.com/zitadel/zitadel/releases/tag/v2.71.9)
2.x versions are fixed on &amp;gt;=[2.70.10](https://github.com/zitadel/zitadel/releases/tag/v2.70.10)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The recommended solution is to update ZITADEL to a patched version.&lt;/p&gt;
&lt;p&gt;### Questions&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Thanks to Józef Chraplewski from Nedap for reporting this vulnerability.&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;### Impact&lt;/p&gt;
&lt;p&gt;ZITADEL offers developers the ability to manage user sessions using the [Session API](https://zitadel.com/docs/category/apis/resources/session_service_v2/session-service). This API enables the use of IdPs for authentication, known as idp intents.&lt;/p&gt;
&lt;p&gt;Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session.&lt;/p&gt;
&lt;p&gt;However, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user.&lt;/p&gt;
&lt;p&gt;It’s important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;3.x versions are fixed on &amp;gt;=[3.0.0](https://github.com/zitadel/zitadel/releases/tag/v3.0.0)
2.71.x versions are fixed on &amp;gt;=[2.71.9](https://github.com/zitadel/zitadel/releases/tag/v2.71.9)
2.x versions are fixed on &amp;gt;=[2.70.10](https://github.com/zitadel/zitadel/releases/tag/v2.70.10)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The recommended solution is to update ZITADEL to a patched version.&lt;/p&gt;
&lt;p&gt;### Questions&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Thanks to Józef Chraplewski from Nedap for reporting this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g4r8-mp7g-85fq</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:15135-1 — govulncheck-vulndb-0.0.20250515T200012-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15135-1</link>
      <description>&lt;p&gt;govulncheck-vulndb-0.0.20250515T200012-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;govulncheck-vulndb-0.0.20250515T200012-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:15135-1</guid>
    </item>
  </channel>
</rss>
