Keycloak has lack of validation of access token on client registrations endpoint
When a service account with the create-client or manage-clients role can use the client-registration endpoints to create/manage clients with an access token.
If the access token is leaked, there is an option to revoke the specific token. However, the check is not performed in client-registration endpoints.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.keycloak:keycloak-core | < 20.0.3 | 20.0.3 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N- Weakness (CWE)
CWE-284, CWE-863- Platform
- Java / Kotlin (Maven)
- Package
org.keycloak:keycloak-core- Disclosed
- 12.01.2023
- Updated
- 11.10.2026 11:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-v436-q368-hvgg - CC BY 4.0
Vulnerability history: org.keycloak:keycloak-core
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
- 49
- First → latest
- 10.2018 02.2025
- Without a fix
- 5
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 14
- Medium 31
- Low 1
Disclosures per year
- 2018: 9
- 2019: 4
- 2020: 4
- 2021: 5
- 2022: 17
- 2023: 4
- 2024: 5
- 2025: 1
- 2026: 0
-
Keycloak has lack of validation of access token on client registrations endpoint 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.