CVE-2026-7500: Keycloak has a Forced Browsing issue
(updated )
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.
References
- access.redhat.com/errata/RHSA-2026:25097
- access.redhat.com/errata/RHSA-2026:25098
- access.redhat.com/security/cve/CVE-2026-7500
- bugzilla.redhat.com/show_bug.cgi?id=2464126
- github.com/advisories/GHSA-hm32-hfmw-rhvg
- github.com/keycloak/keycloak/issues/48709
- github.com/keycloak/keycloak/pull/48715
- nvd.nist.gov/vuln/detail/CVE-2026-7500
Code Behaviors & Features
Detect and mitigate CVE-2026-7500 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →