Advisory record · GHSA-6rrr-78xp-5jp8

Zitadel RefreshToken invalidation vulnerability

CVSS 5.9 MediumEPSS 0.0065 · 52nd percentile

Published by the GitHub Advisory Database at 11 Jan 2023, 18:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/zitadel/zitadelGo>=2.17.0, <2.17.3 || >=2.0.0, <2.16.42.17.3, 2.16.4
Identifiers
GHSA-6rrr-78xp-5jp8 · CVE-2023-22492
Weakness (CWE)
CWE-613
Published
11 Jan 2023
Updated
10 Sept 2026

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.

Written 5 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:43 UTC First seen by agentprime
  2. 31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.