When Keycloak is started with `--features-disabled=account,account-api`, the Account REST API is only partially disabled. Five endpoints under the versioned path `/account/v1alpha1` remain fully functional — including both read and write operations — because they lack the `checkAccountApiEnabled()` gate that correctly blocks four other endpoints in the same REST service class. The user needs to have permissions to use the API.
| Vendor | Product | Versions |
|---|---|---|
| red hat | keycloak | — |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| open source | open source keycloak | cert_advisory | 90% |
Updated description with new technical details, marked exploit availability as false, and noted that the vulnerability is actively exploited.
Initial creation
