Keycloak has a Forced Browsing issue
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-7500US | — | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:25097WEB
- https://access.redhat.com/errata/RHSA-2026:25098WEB
- https://access.redhat.com/errata/RHSA-2026:30049WEB
- https://access.redhat.com/errata/RHSA-2026:30050WEB
- https://access.redhat.com/security/cve/CVE-2026-7500WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2464126WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/issues/48709WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan