Keycloak has a Forced Browsing issue
Moderate severity
GitHub Reviewed
Published
Apr 30, 2026
to the GitHub Advisory Database
•
Updated May 7, 2026
Description
Published by the National Vulnerability Database
Apr 30, 2026
Published to the GitHub Advisory Database
Apr 30, 2026
Reviewed
May 7, 2026
Last updated
May 7, 2026
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/v1alpha1remain fully functional — including both read and write operations — because they lack thecheckAccountApiEnabled()gate that correctly blocks four other endpoints in the same REST service class. The user needs to have permissions to use the API.References