Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Zitadel versions 2.0.0 up to 2.16.4 and 2.17.0 up to 2.17.3 are affected. Refresh tokens were not invalidated when a user was locked or deactivated, so such a user could still obtain valid access tokens through a refresh token grant until the configured RefreshTokenExpiration passed. Upgrade to Zitadel 2.16.4 or 2.17.3; as a workaround, set RefreshTokenExpiration in the instance's OIDC settings to match your security requirements.
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 |
|---|---|---|---|---|
| 5.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0065, the 52nd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:43 UTC First seen by agentprime
- 31 Oct 2026, 14:43 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6rrr-78xp-5jp8
- OSV: GHSA-6rrr-78xp-5jp8
- github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8
- nvd.nist.gov/vuln/detail/CVE-2023-22492
- github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83
- github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2
- github.com/zitadel/zitadel
- github.com/zitadel/zitadel/releases/tag/v2.16.4
- github.com/zitadel/zitadel/releases/tag/v2.17.3