Keycloak vulnerable to impersonation via logout token exchange
Keycloak was found to not properly enforce token types when validating signatures locally. An authenticated attacker could use this flaw to exchange a logout token for an access token and possibly gain access to data outside of enforced permissions.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.keycloak:keycloak-services | < 22.0.10, >= 23.0.0, < 24.0.3 | 22.0.10, 24.0.3 |
References
- https://github.com/keycloak/keycloak/security/advisories/GHSA-7fpj-9hr8-28vh
- https://nvd.nist.gov/vuln/detail/CVE-2023-0657
- https://access.redhat.com/errata/RHSA-2024:1867
- https://access.redhat.com/errata/RHSA-2024:1868
- https://access.redhat.com/security/cve/CVE-2023-0657
- https://bugzilla.redhat.com/show_bug.cgi?id=2166728
- https://github.com/keycloak/keycloak
- CVSS vector
CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N- Weakness (CWE)
CWE-273, CWE-284, CWE-287, CWE-290, CWE-347- Platform
- Java / Kotlin (Maven)
- Package
org.keycloak:keycloak-services- Disclosed
- 17.04.2024
- Updated
- 11.10.2026 13:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-7fpj-9hr8-28vh - CC BY 4.0
Vulnerability history: org.keycloak:keycloak-services
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 98
- First → latest
- 01.2022 08.2026
- Without a fix
- 16
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 26
- Medium 51
- Low 18
Disclosures per year
- 2022: 9
- 2023: 9
- 2024: 17
- 2025: 11
- 2026: 52
-
Keycloak vulnerable to impersonation via logout token exchange this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.