Org.keycloak.keycloak-services: improper access control on keycloak server when the account account api feature is disabled
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.2%
exploitation probability
0.2%top 86% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Affected products
Red Hat · Red Hat build of Keycloak 26.4Red Hat · Red Hat build of Keycloak 26.4.13Red Hat · Red Hat build of Keycloak 26.6Red Hat · Red Hat build of Keycloak 26.6.3References
https://access.redhat.com/errata/RHSA-2026:25097https://access.redhat.com/errata/RHSA-2026:25098https://access.redhat.com/errata/RHSA-2026:30049https://access.redhat.com/errata/RHSA-2026:30050https://access.redhat.com/security/cve/CVE-2026-7500https://bugzilla.redhat.com/show_bug.cgi?id=2464126