<?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 12:17:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335723</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335723</link>
      <description>EUVD-2026-335723</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335723</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56665</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56665</link>
      <description>&lt;p&gt;ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL is an open source identity management platform. From 3.0.0-rc.1 through 3.4.11 and from 4.0.0-rc.1 through 4.15.1, ZITADEL&amp;#39;s external JWT Identity Provider validation in internal/idp/providers/jwt/session.go skips expiration handling when an incoming token omits the exp claim, allowing a token from a trusted issuer to be treated as valid without an automatic expiration window. This issue is fixed in versions 3.4.12 and 4.15.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL is an open source identity management platform. From 3.0.0-rc.1 through 3.4.11 and from 4.0.0-rc.1 through 4.15.1, ZITADEL&amp;#39;s external JWT Identity Provider validation in internal/idp/providers/jwt/session.go skips expiration handling when an incoming token omits the exp claim, allowing a token from a trusted issuer to be treated as valid without an automatic expiration window. This issue is fixed in versions 3.4.12 and 4.15.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56665</guid>
    </item>
    <item>
      <title>GHSA-v77h-2w3m-94hx — ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v77h-2w3m-94hx</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 token lifecycle validation vulnerability was discovered in ZITADEL&amp;#39;s external JWT Identity Provider (IdP) implementation
Specifically, within the validation pipeline, if an incoming JWT omits the `exp` claim entirely, the expiration block is silently skipped rather than rejected. The token is treated as valid forever.&lt;/p&gt;
&lt;p&gt;Per the OIDC Core 1.0 specification, identity token validation pipelines must strictly handle and enforce session expiration. ZITADEL&amp;#39;s silent acceptance of tokens missing these temporal constraints compromises session integrity.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker in possession of a token lacking an `exp` claim holds a permanent credential with no automatic expiration or revocation window.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Systems running one of the following versions are affected:&lt;/p&gt;
&lt;p&gt;* **4.x**: `4.0.0` through `4.15.1` (including RC versions)
* **3.x**: `3.0.0` through `3.4.11` (including RC versions)&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. ZITADEL now explicitly rejects tokens that lack an `exp` claim.&lt;/p&gt;
&lt;p&gt;* **4.x**: Upgrade to $\ge$ [4.15.2](https://github.com/zitadel/zitadel/releases/tag/v4.15.2)
* **3.x**: Upgrade to $\ge$ [3.4.12](https://github.com/zitadel/zitadel/releases/tag/v3.4.12)&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;If an immediate upgrade is not feasible, ensure at the upstream Identity Provider level that an external IdP explicitly includes the `exp` claim in all signed J…&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 token lifecycle validation vulnerability was discovered in ZITADEL&amp;#39;s external JWT Identity Provider (IdP) implementation
Specifically, within the validation pipeline, if an incoming JWT omits the `exp` claim entirely, the expiration block is silently skipped rather than rejected. The token is treated as valid forever.&lt;/p&gt;
&lt;p&gt;Per the OIDC Core 1.0 specification, identity token validation pipelines must strictly handle and enforce session expiration. ZITADEL&amp;#39;s silent acceptance of tokens missing these temporal constraints compromises session integrity.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker in possession of a token lacking an `exp` claim holds a permanent credential with no automatic expiration or revocation window.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Systems running one of the following versions are affected:&lt;/p&gt;
&lt;p&gt;* **4.x**: `4.0.0` through `4.15.1` (including RC versions)
* **3.x**: `3.0.0` through `3.4.11` (including RC versions)&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed in the latest releases. ZITADEL now explicitly rejects tokens that lack an `exp` claim.&lt;/p&gt;
&lt;p&gt;* **4.x**: Upgrade to $\ge$ [4.15.2](https://github.com/zitadel/zitadel/releases/tag/v4.15.2)
* **3.x**: Upgrade to $\ge$ [3.4.12](https://github.com/zitadel/zitadel/releases/tag/v3.4.12)&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;If an immediate upgrade is not feasible, ensure at the upstream Identity Provider level that an external IdP explicitly includes the `exp` claim in all signed J…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v77h-2w3m-94hx</guid>
    </item>
  </channel>
</rss>
