keycloak/keycloak · Security
Keycloak has a Forced Browsing issue
- GHSA ID
- GHSA-hm32-hfmw-rhvg
- CVE ID
- CVE-2026-7500
- Severity
- medium
- Published
- Updated
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CVSS v3
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
CWEs
- CWE-425 · Direct Request ('Forced Browsing')
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-7500 ↗
- https://access.redhat.com/security/cve/CVE-2026-7500 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2464126 ↗
- https://github.com/keycloak/keycloak/issues/48709 ↗
- https://github.com/keycloak/keycloak/pull/48715 ↗
- https://access.redhat.com/errata/RHSA-2026:25098 ↗
- https://access.redhat.com/errata/RHSA-2026:25097 ↗
- https://access.redhat.com/errata/RHSA-2026:30049 ↗
- https://access.redhat.com/errata/RHSA-2026:30050 ↗
- https://github.com/advisories/GHSA-hm32-hfmw-rhvg ↗