CVE-2026-9792
Redhat Build Of Keycloak
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2026-9792 is a medium-severity Improper Handling of Insufficient Permissions or Privileges (CWE-280) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32708
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Direct remote unauthenticated exploitation of a policy bypass flaw in the public-facing Keycloak OIDC service to obtain access tokens.
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces the reject-ropc-grant decision so that ROPC token issuance is blocked when client policies are configured, preventing the described bypass.
Restricts ROPC grant usage to only explicitly authorized clients and roles, limiting the impact of any condition-provider bypass in Keycloak policies.
Enforces information-flow rules on OAuth token grants, ensuring ROPC flows cannot circumvent the intended client-policy restrictions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Defining, enforcing and reviewing access permissions with least privilege directly prevents code paths that mishandle insufficient privileges.
Runtime monitoring of software and data surfaces adverse events triggered by unhandled permission failures.
Generating logs of permission-related events enables detection and analysis of improper handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing or incorrect privilege handling.
Defines access-control policy that should prevent insufficient-privilege situations.
Specifies how access rights are granted, reviewed and revoked, directly addressing privilege handling.
Requires explicit management of privileged access rights, reducing the chance of missing privilege checks.
Secure-SDLC practices include privilege checks during design and coding.
Secure-coding standards require proper permission checks before resource access.
Hardening callouts derived
Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).
Oracle Linux 8 (1 rule)
- V-248548 OL 8 must use a Linux Security Module configured to enforce limits on system services. via CWE-280