<?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 08:14:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335710</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335710</link>
      <description>EUVD-2026-335710</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335710</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56664</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56664</link>
      <description>&lt;p&gt;ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL&amp;#39;s external JWT Identity Provider validation in internal/idp/providers/jwt/session.go skips the maximum token age freshness check when an incoming token omits the iat claim, allowing arbitrarily old tokens from a trusted issuer to pass authentication. 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&amp;#39;s external JWT Identity Provider validation in internal/idp/providers/jwt/session.go skips the maximum token age freshness check when an incoming token omits the iat claim, allowing arbitrarily old tokens from a trusted issuer to pass authentication. 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-56664</guid>
    </item>
    <item>
      <title>GHSA-wxg7-w2v3-w38g — ZITADEL: Missing Token Lifecyle Validation (`exp` and `iat`) in JWT IdP Provider</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wxg7-w2v3-w38g</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.
ZITADEL enforces a 1-hour maximum token age freshness window (`maxAge`) calculated from the token&amp;#39;s issue time. However, this safety check is guarded by a presence condition. If an incoming token omits the `iat` claim, the freshness check is entirely bypassed, allowing arbitrarily old tokens to pass authentication successfully.&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 stale token lacking an `iat` claim can reuse it indefinitely without triggering the maximum age freshness invalidation.&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 `iat` 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 u…&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.
ZITADEL enforces a 1-hour maximum token age freshness window (`maxAge`) calculated from the token&amp;#39;s issue time. However, this safety check is guarded by a presence condition. If an incoming token omits the `iat` claim, the freshness check is entirely bypassed, allowing arbitrarily old tokens to pass authentication successfully.&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 stale token lacking an `iat` claim can reuse it indefinitely without triggering the maximum age freshness invalidation.&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 `iat` 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 u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wxg7-w2v3-w38g</guid>
    </item>
  </channel>
</rss>
