Skip to main content

Red Hat Keycloak CVE-2026-7500

| EUVDEUVD-2026-26381 MEDIUM
Direct Request ('Forced Browsing') (CWE-425)
2026-04-30 redhat
5.4
CVSS 3.1 · Vendor: redhat
Share

Severity by source

Vendor (redhat) PRIMARY
5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Red Hat
5.4 MEDIUM
qualitative

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

4
Analysis Generated
Apr 30, 2026 - 15:30 vuln.today
EUVD ID Assigned
Apr 30, 2026 - 15:00 euvd
EUVD-2026-26381
Analysis Generated
Apr 30, 2026 - 15:00 vuln.today
CVE Published
Apr 30, 2026 - 14:53 nvd
MEDIUM 5.4

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 76 maven packages depend on org.keycloak:keycloak-services (42 direct, 34 indirect)

Ecosystem-wide dependent count for version 26.6.1.

DescriptionCVE.org

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.

AnalysisAI

Keycloak's Account REST API remains partially accessible even when explicitly disabled via the --features-disabled=account,account-api flag, allowing authenticated users to read and modify account data through five unprotected endpoints under /account/v1alpha1/ that lack the required checkAccountApiEnabled() access control gate present in four sibling endpoints within the same service class.

Technical ContextAI

Keycloak's Account REST API is designed to be disabled entirely via the --features-disabled feature flag mechanism, which gates API endpoints through a checkAccountApiEnabled() validation function. However, five endpoints under the versioned path /account/v1alpha1/ were not instrumented with this guard, representing an incomplete implementation of the feature disable logic. This is a control-flow bypass in the authorization layer (CWE-425: Direct Request ('Fire-and-Forget') Execution) where certain API routes escape the intended access control checks that protect the feature flag. The vulnerability affects Red Hat Build of Keycloak across all versions prior to the patch, as indicated by the CPE wildcard matching any version.

RemediationAI

Upgrade Keycloak to the patched version released by Red Hat for CVE-2026-7500, available via https://access.redhat.com/security/cve/CVE-2026-7500. The patch instruments all five vulnerable endpoints with the missing checkAccountApiEnabled() access control gate to ensure the feature flag is consistently enforced across the entire Account REST API surface. Until patching is possible, implement network-level access controls to restrict access to the /account/v1alpha1/ endpoints at the ingress or reverse proxy layer (e.g., deny traffic to paths matching /account/v1alpha1/*), though this workaround may break legitimate account management features if clients rely on versioned endpoints. Alternatively, disable Keycloak's Account REST API entirely at the application level by removing the account management feature from your deployment if it is not required, or segregate user access such that only trusted administrators can authenticate to Keycloak instances with account features disabled.

CVE-2026-18963 CRITICAL POC
9.1 Aug 18

Account takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in

CVE-2026-16442 CRITICAL
9.8 Aug 05

Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML

CVE-2026-16443 CRITICAL
9.1 Aug 05

Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge

CVE-2026-15572 HIGH
8.8 Aug 05

Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil

CVE-2026-9800 HIGH
8.1 Jun 25

Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con

CVE-2026-15573 HIGH
8.1 Aug 05

URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re

CVE-2026-16102 HIGH
8.1 Aug 05

Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou

CVE-2026-18214 HIGH
8.1 Jul 31

Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho

CVE-2026-11800 HIGH
8.1 Jun 25

Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re

CVE-2026-18215 HIGH
8.1 Jul 31

Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro

CVE-2026-18967 HIGH
8.1 Aug 06

Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut

CVE-2026-7504 HIGH
8.1 May 19

Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus

Vendor StatusVendor

Share

CVE-2026-7500 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy