Answer in brief
CVE-2026-7500 records a Medium severity (CVSS 5.4) vulnerability in Keycloak has a Forced Browsing issue. The current sources do not mark it as known exploited. The current feed maps org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.keycloak:keycloak-servicesmaven | <=26.6.1 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=0 | Not reported |
Published upstream
Apr 30, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.