Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
ZITADEL's external JWT Identity Provider implementation does not validate the audience (aud) claim of tokens, so any validly signed token from a trusted issuer is accepted. An attacker who holds a valid token from that issuer, issued for a different service, could authenticate to ZITADEL as that user. Upgrade to 4.15.2 or later for 4.x, or to 3.4.12 or later for 3.x; the fix lets administrators set a required audience in the IdP configuration. Affected versions are 4.0.0 through 4.11.0 and 3.0.0 through 3.4.11, including release candidates.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.2 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0015, the 4th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:07 UTC First seen by agentprime
- 31 Oct 2026, 15:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-g5h5-m4hm-xjrr
- OSV: GHSA-g5h5-m4hm-xjrr
- github.com/zitadel/zitadel/security/advisories/GHSA-g5h5-m4hm-xjrr
- github.com/zitadel/zitadel/commit/d184e976fc799a383bb6ef9f32c3bae11a3ef85f
- github.com/zitadel/zitadel
- github.com/zitadel/zitadel/releases/tag/v3.4.12
- github.com/zitadel/zitadel/releases/tag/v4.15.2