# CVE-2023-22492: RefreshToken invalidation vulnerability

> Attackers can obtain valid access tokens using refresh tokens even after user accounts are locked or deactivated, bypassing authentication controls.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-6rrr-78xp-5jp8

## What is CVE-2023-22492?

CVE-2023-22492 is a medium-severity authentication bypass vulnerability in zitadel, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZITADEL is a combination of Auth0 and Keycloak. RefreshTokens is an OAuth 2.0 feature that allows applications to retrieve new access tokens and refresh the user's session without the need for interacting with a UI. RefreshTokens were not invalidated when a user was locked or deactivated. The deactivated or locked user was able to obtain a valid access token only through a refresh token grant. When the locked or deactivated user’s session was already terminated (“logged out”) then it was not possible to create a new session. Renewal of access token through a refresh token grant is limited to the configured amount of time (RefreshTokenExpiration). As a workaround, ensure the RefreshTokenExpiration in the OIDC settings of your instance is set according to your security requirements. This issue has been patched in versions 2.17.3 and 2.16.4.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2023-22492?

4 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zitadel/zitadel` | Go | From 2.0.0 | 2.16.4 |
| `github.com/zitadel/zitadel` | Go | From 2.0.0 | 2.16.4 |
| `github.com/zitadel/zitadel` | Go | From 2.17.0 | 2.17.3 |
| `github.com/zitadel/zitadel` | Go | From 2.17.0 | 2.17.3 |

Products: Zitadel Zitadel.

## How do I fix CVE-2023-22492?

Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 2.16.4 or 2.17.3.

## Is CVE-2023-22492 being exploited?

There is no known exploitation of CVE-2023-22492 in the wild and no public exploit code.

## Other vulnerabilities in zitadel

- [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3)
- [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3)
- [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0)
- [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7)
- [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22492 and fix it if it is affected.

What it is: CVE-2023-22492 is a medium-severity authentication bypass vulnerability in zitadel, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22492 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zitadel/zitadel (Go): affected from 2.0.0; fixed in 2.16.4
- github.com/zitadel/zitadel (Go): affected from 2.0.0; fixed in 2.16.4
- github.com/zitadel/zitadel (Go): affected from 2.17.0; fixed in 2.17.3
- github.com/zitadel/zitadel (Go): affected from 2.17.0; fixed in 2.17.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22492/ (Markdown: https://insights.sbomify.com/CVE-2023-22492/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22492
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22492
- OSV: https://osv.dev/vulnerability/CVE-2023-22492

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22492/
Summaries are generated and may contain mistakes; the official description above is the record.