CVE-2026-56665 ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
Attackers can use expired JWT tokens from trusted issuers to bypass authentication in ZITADEL due to missing expiration validation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-56665?
CVE-2026-56665 is a medium-severity authentication bypass vulnerability in zitadel, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-613
Which versions are affected by CVE-2026-56665?
5 open source packages ship an affected version, including github.com/zitadel/zitadel.
| Package | Affected | Fixed in |
|---|---|---|
github.com/zitadel/zitadel Go | All versions | None |
github.com/zitadel/zitadel Go | All versions | 3.4.12 |
github.com/zitadel/zitadel Go | All versions | 3.4.12 |
github.com/zitadel/zitadel Go | From 4.0.0-rc.1 | 4.15.2 |
github.com/zitadel/zitadel Go | From 4.0.0-rc.1 | 4.15.2 |
How do I fix CVE-2026-56665?
Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 3.4.12 or 4.15.2.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-56665 being exploited?
There is no known exploitation of CVE-2026-56665 in the wild and no public exploit code.
Sources
Also known as GHSA-v77h-2w3m-94hx, GO-2026-6469.