CVE-2026-7500
When Keycloak is started with …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-7500
- bugzilla.redhat.com/show_bug.cgi?id=2464126
- nvd.nist.gov/vuln/detail/CVE-2026-7500
- github.com/keycloak/keycloak/issues/48709
- github.com/keycloak/keycloak/pull/48715
- github.com/advisories/GHSA-hm32-hfmw-rhvg
- access.redhat.com/errata/RHSA-2026:25098
- access.redhat.com/errata/RHSA-2026:25097
- nvd.nist.gov/vuln/detail/CVE-2026-7500
- cve.org/CVERecord?id=CVE-2026-7500
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.