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.
CVE-2026-56665
This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(low)
- EPSS
- 6.3%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (5)
Auto-updated Jul 10, 2026Missing Token Expiration (`exp`) Validation in JWT IdP Provider · Advisory · zitadel/zitadel · GitHub
https://github.com/zitadel/zitadel/security/advisories/GHSA-v77h-2w3m-94hxv4.15.2
Patch available: zitadel/zitadel v4.15.2
https://github.com/zitadel/zitadel/releases/tag/v4.15.2v3.4.12
Patch available: zitadel/zitadel v3.4.12
https://github.com/zitadel/zitadel/releases/tag/v3.4.12commit d1c3aa84af8f (zitadel/zitadel)
Fix landed in zitadel/zitadel commit d1c3aa84af8f — awaiting tagged release
https://github.com/zitadel/zitadel/commit/d1c3aa84af8fcb0f33910ada30b866f4afb551accommit 4925fab849d3 (zitadel/zitadel)
Fix landed in zitadel/zitadel commit 4925fab849d3 — awaiting tagged release
https://github.com/zitadel/zitadel/commit/4925fab849d39a88674485d937b79e54318b48a8Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 17:56 UTCEG score recompute
- 2026-07-10 17:53 UTCEG score recompute
- 2026-07-10 17:52 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-56665?
When was CVE-2026-56665 disclosed?
Is CVE-2026-56665 actively exploited?
What is the CVSS score of CVE-2026-56665?
How do I remediate CVE-2026-56665?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56665
Is Your Infrastructure Affected by CVE-2026-56665?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.