Description
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.
Problem types
Direct Request ('Forced Browsing')
Product status
Timeline
| 2026-04-30: | Reported to Red Hat. |
| 2026-04-30: | Made public. |
Credits
Red Hat would like to thank Evan Hendra for reporting this issue.
References
access.redhat.com/security/cve/CVE-2026-7500
bugzilla.redhat.com/show_bug.cgi?id=2464126 (RHBZ#2464126)