ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL'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.
CVE-2026-56664
MEDIUMPre-NVD 4.24.2Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
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).
Triggered by: NVD CVSS baseline
Sources: secondary
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.2Exploit: NoneExposed: 0
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
- 10.3%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (5)
Auto-updated Jul 10, 2026Patch available. Sources: github_commit, github_release, github.
github Patch Available
Missing Issued-At (`iat`) Freshness Validation in JWT IdP Provider · Advisory · zitadel/zitadel · GitHub
https://github.com/zitadel/zitadel/security/advisories/GHSA-wxg7-w2v3-w38ggithub_release Patch Available
v4.15.2
Patch available: zitadel/zitadel v4.15.2
https://github.com/zitadel/zitadel/releases/tag/v4.15.2github_release Patch Available
v3.4.12
Patch available: zitadel/zitadel v3.4.12
https://github.com/zitadel/zitadel/releases/tag/v3.4.12github_commit
commit d1c3aa84af8f (zitadel/zitadel)
Fix landed in zitadel/zitadel commit d1c3aa84af8f — awaiting tagged release
https://github.com/zitadel/zitadel/commit/d1c3aa84af8fcb0f33910ada30b866f4afb551acgithub_commit
commit 4925fab849d3 (zitadel/zitadel)
Fix landed in zitadel/zitadel commit 4925fab849d3 — awaiting tagged release
https://github.com/zitadel/zitadel/commit/4925fab849d39a88674485d937b79e54318b48a8Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/zitadel/zitadel | — | 1.80.0-v2.20.0.20260615122908-fad02c6d9f45 | — |
Weakness 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:21 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-56664?
CVE-2026-56664 is a medium vulnerability published on July 10, 2026. ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL'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…
When was CVE-2026-56664 disclosed?
CVE-2026-56664 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56664 actively exploited?
CVE-2026-56664 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56664?
CVE-2026-56664 has a CVSS v3 base score of 4.2 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-56664?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56664, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56664
Is Your Infrastructure Affected by CVE-2026-56664?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.