cve.bz

CVE-2026-9792 redhat build of keycloak

6.5 mediumEPSS 0.3%Fix available

Medium (6.5) in redhat build of keycloak. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.keycloak:keycloak-services 26.6.3.

On this page
A flaw was found in Keycloak's Client Policies, specifically within the `org.keycloak.protocol.oidc` component. When certain condition providers (client-type, client-roles, client-attributes, client-scopes) are used to enforce security restrictions, the `reject-ropc-grant` executor is silently bypassed. This allows an unauthenticated remote attacker to obtain tokens via a Resource Owner Password Credentials (ROPC) grant, even when a policy is explicitly configured to block it. This bypass can lead to unauthorized access and information disclosure.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-280 Improper Handling of Insufficient Permissions or Privileges
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-9792 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9792?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9792?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9792 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-9792

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-9792](https://cve.bz/cve/badge/CVE-2026-9792.svg)](https://cve.bz/cve/CVE-2026-9792)

HTML:

<a href="https://cve.bz/cve/CVE-2026-9792"><img src="https://cve.bz/cve/badge/CVE-2026-9792.svg" alt="CVE-2026-9792"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.426.4.13-1
Red Hat build of Keycloak 26.426.4-19
Red Hat build of Keycloak 26.626.6.3-3
Red Hat build of Keycloak 26.626.6-6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-33j3-g875-37rpMavenorg.keycloak:keycloak-services>=26.5.0 <26.6.326.6.3
GHSA-33j3-g875-37rpMavenorg.keycloak:keycloak-services<=26.4.7no fix published

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Medium severity flaw in Keycloak allows client policies designed to reject Resource Owner Password Credentials (ROPC) grants to be bypassed. When specific condition providers (client-type, client-roles, client-attributes, or client-scopes) are used, clients can obtain tokens via ROPC despite explicit policy configuration to block such requests. This impacts Keycloak deployments where administrators rely on these policies to enforce FAPI 2.0 compliance and prevent credential exposure.

Red Hat's mitigation

To mitigate this issue, Keycloak administrators should review and adjust client policies designed to reject Resource Owner Password Credentials (ROPC) grants. Avoid using the `client-type`, `client-roles`, `client-attributes`, or `client-scopes` condition providers in conjunction with the `reject-ropc-grant` executor. Instead, configure policies to use the `grant-type` condition provider for ROPC rejection. A restart or reload of the Keycloak service may be required for these policy changes to take full effect.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.13-1Fixed 2026-06-25RHSA-2026:30050
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9:26.4-19Fixed 2026-06-25RHSA-2026:30050
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator:26.4-19Fixed 2026-06-25RHSA-2026:30050
Red Hat build of Keycloak 26.4.13rhbk/keycloak-rhel9Fixed 2026-06-25RHSA-2026:30049
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.3-3Fixed 2026-06-10RHSA-2026:25097
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9:26.6-6Fixed 2026-06-10RHSA-2026:25097
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator:26.6-6Fixed 2026-06-10RHSA-2026:25097
Red Hat build of Keycloak 26.6.3rhbk/keycloak-rhel9Fixed 2026-06-10RHSA-2026:25098

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-9792.

References

Check your stackJSON