https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T09:44:59.381471+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-335723 EUVD-2026-335723 2026-10-06T09:44:59.425535+00:00 EUVD-2026-335723 https://cve.radiocsirt.org/vuln/fkie_cve-2026-56665 fkie_cve-2026-56665 2026-10-06T09:44:59.425570+00:00

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'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.

 https://cve.radiocsirt.org/vuln/ghsa-v77h-2w3m-94hx GHSA-v77h-2w3m-94hx — ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider 2026-10-06T09:44:59.425610+00:00

Affected: Go: github.com/zitadel/zitadel

### Summary

A token lifecycle validation vulnerability was discovered in ZITADEL'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.

Per the OIDC Core 1.0 specification, identity token validation pipelines must strictly handle and enforce session expiration. ZITADEL's silent acceptance of tokens missing these temporal constraints compromises session integrity.

### Impact

An attacker in possession of a token lacking an `exp` claim holds a permanent credential with no automatic expiration or revocation window.

### Affected Versions

Systems running one of the following versions are affected:

* **4.x**: `4.0.0` through `4.15.1` (including RC versions) * **3.x**: `3.0.0` through `3.4.11` (including RC versions)

### Patches

The vulnerability has been addressed in the latest releases. ZITADEL now explicitly rejects tokens that lack an `exp` claim.

* **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)

### Workarounds

The recommended solution is to update ZITADEL to a patched version.

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…