# Zitadel RefreshToken invalidation vulnerability

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

- **Identifiers:** `GHSA-6rrr-78xp-5jp8` · `CVE-2023-22492`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 11 Jan 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/zitadel/zitadel` (Go): affected `>=2.17.0, <2.17.3 || >=2.0.0, <2.16.4`; fixed in `2.17.3`, `2.16.4`

## 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

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N`, from 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](https://osv.dev/vulnerability/GHSA-6rrr-78xp-5jp8)

## Sources

- [GitHub Advisory Database: GHSA-6rrr-78xp-5jp8](https://github.com/advisories/GHSA-6rrr-78xp-5jp8)
- [OSV: GHSA-6rrr-78xp-5jp8](https://osv.dev/vulnerability/GHSA-6rrr-78xp-5jp8)
- <https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-22492>
- <https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83>
- <https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2>
- <https://github.com/zitadel/zitadel>
- <https://github.com/zitadel/zitadel/releases/tag/v2.16.4>
- <https://github.com/zitadel/zitadel/releases/tag/v2.17.3>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6rrr-78xp-5jp8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6rrr-78xp-5jp8/>. Everything for agents: <https://agentprime.io/llms.txt>.
