Improper Handling of Insufficient Permissions or Privileges Affecting org.keycloak:keycloak-services package, versions [,26.6.3)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Handling of Insufficient Permissions or Privileges vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGKEYCLOAK-17082623
- published29 May 2026
- disclosed28 May 2026
- creditEvan Hendra
Introduced: 28 May 2026
CVE-2026-9792 (opens in a new tab)How to fix?
Upgrade org.keycloak:keycloak-services to version 26.6.3 or higher.
Overview
org.keycloak:keycloak-services is an open source identity and access management solution for modern applications and services.
Affected versions of this package are vulnerable to Improper Handling of Insufficient Permissions or Privileges in the org.keycloak.protocol.oidc component when specific condition providers such as client-type, client-roles, client-attributes, or client-scopes are used. An attacker can gain unauthorized access and obtain authentication tokens by bypassing configured policy restrictions through Resource Owner Password Credentials (ROPC) grants, even when policies are set to block such requests. This is only exploitable if client policies rely on these condition providers to enforce ROPC grant rejection.
Workaround
This vulnerability can be mitigated by configuring policies to use the grant-type condition provider for ROPC rejection and avoiding the use of client-type, client-roles, client-attributes, or client-scopes condition providers in conjunction with the reject-ropc-grant executor. A restart or reload of the service may be required for policy changes to take effect.