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.

Project Subscriptions

Vendors Products
Build Keycloak Subscribe
Build Of Keycloak Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-hm32-hfmw-rhvg Keycloak has a Forced Browsing issue
Fixes

Solution

No solution given by the vendor.


Workaround

To reduce the attack surface, restrict network access to the Keycloak server's administration and API endpoints to trusted networks or hosts. This limits the ability of unauthorized users to interact with the server and potentially exploit this improper access control vulnerability. If the Keycloak service is reloaded or restarted, ensure that firewall rules or network access controls remain in effect.

History

Tue, 05 May 2026 03:00:00 +0000

Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*

Fri, 01 May 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Thu, 30 Apr 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Redhat build Of Keycloak
Vendors & Products Redhat build Of Keycloak

Thu, 30 Apr 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 30 Apr 2026 15:00:00 +0000

Type Values Removed Values Added
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.
Title Org.keycloak.keycloak-services: improper access control on keycloak server when the account account api feature is disabled
First Time appeared Redhat
Redhat build Keycloak
Weaknesses CWE-425
CPEs cpe:/a:redhat:build_keycloak:
Vendors & Products Redhat
Redhat build Keycloak
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-04-30T15:10:45.325Z

Reserved: 2026-04-30T14:32:50.005Z

Link: CVE-2026-7500

cve-icon Vulnrichment

Updated: 2026-04-30T15:06:53.790Z

cve-icon NVD

Status : Analyzed

Published: 2026-04-30T15:16:23.673

Modified: 2026-05-05T03:00:08.177

Link: CVE-2026-7500

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-04-30T00:00:00Z

Links: CVE-2026-7500 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-05T04:30:15Z

Weaknesses