EUVD-2026-30881
GHSA-933f-rg6j-f46p
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
1Blast Radius
ecosystem impact- 50 maven packages depend on org.keycloak:keycloak-services (22 direct, 28 indirect)
Ecosystem-wide dependent count for version 26.5.0.
DescriptionCVE.org
A flaw was found in Keycloak. A broken access control vulnerability in the Account Resources user lookup endpoint allows a remote authenticated user, who owns at least one User-Managed Access (UMA) resource, to enumerate and harvest personally identifiable information (PII) for all realm users. By sending crafted requests with arbitrary usernames or email values, the endpoint returns full profile objects for unrelated users. This leads to broad profile-level information disclosure.
AnalysisAI
Broken access control in Keycloak's Account Resources user lookup endpoint exposes full PII profiles of all realm users to any authenticated user who owns at least one User-Managed Access (UMA) resource. By sending crafted requests with arbitrary usernames or email values to this endpoint, the attacker receives complete profile objects for unrelated realm members - bypassing the intended per-user data isolation. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog, but the low attack complexity and minimal privilege requirement (any UMA resource owner) make it a meaningful insider-threat and tenant-isolation risk in shared Keycloak deployments.
Technical ContextAI
Keycloak's User-Managed Access (UMA) implementation extends OAuth 2.0 to allow end-users to manage fine-grained access policies on their own resources. The Account Resources API endpoint, designed to let a resource owner query access details, performs insufficient granularity of access control (CWE-1220) - it fails to scope returned user-profile data to only those users with a legitimate relationship to the requesting party's resources. Instead, it resolves and returns full user profile objects for any username or email submitted, effectively treating the endpoint as an unauthenticated-equivalent user directory. The affected product is Red Hat Build of Keycloak, tracked under CPE cpe:2.3:a:red_hat:red_hat_build_of_keycloak:*:*:*:*:*:*:*:*, with the wildcard version indicating all currently evaluated builds are in scope.
RemediationAI
No vendor-released patch version has been identified at time of analysis; the CPE entry carries a wildcard version with no fixed-version counterpart confirmed in the referenced data. Organizations should monitor the Red Hat Security Advisory at https://access.redhat.com/security/cve/CVE-2026-37981 and the Bugzilla tracker at https://bugzilla.redhat.com/show_bug.cgi?id=2455326 for patch availability. As a compensating control, administrators should audit which realm users have UMA resource ownership and restrict UMA feature enablement to only those deployments where it is operationally required - disabling UMA eliminates access to the vulnerable endpoint but removes resource-sharing delegation functionality. Additionally, network-layer access controls restricting the Account Resources API to trusted internal clients or service accounts can reduce exposure surface while awaiting a patch. Enforce least-privilege policies so that UMA resource ownership is not inadvertently granted to untrusted users.
More in Red Hat Build Of Keycloak
View allAccount takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in
Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge
Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil
Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con
URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re
Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou
Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho
Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro
Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut
Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus
Same technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today