CVE-2026-9791: Red Hat build of Keycloak 26.4 · Incorrect Authorization
Affects Red Hat build of Keycloak 26.4Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4.13 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6.3 | Affected– | Fixed in– |
AI-suggested
Red Hat has released updated Keycloak 26.6.3 images that include fixes for CVE-2026-9791 along with other vulnerabilities. Users should back up their existing installations and upgrade to these updated images as recommended in the Red Hat advisories (RHSA-2026:25097 and RHSA-2026:25098). Patch status is not explicitly confirmed for this CVE alone, but the vendor advisory indicates remediation is included in the new 26.6.3 release. Users should consult the official Red Hat advisory for detailed update instructions.
Description
A flaw was found in Keycloak. An authenticated user with existing organization membership can exploit this flaw by accessing user-facing APIs, such as the account API or by requesting an OpenID Connect (OIDC) token with the 'organization' scope. This allows organization metadata to be disclosed in tokens, even after an administrator has explicitly disabled the Organizations feature, potentially leading to incorrect authorization decisions by resource servers.
References
- access.redhat.com/errata/RHSA-2026:25097 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:25098 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30049 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30050 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-9791 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2482458 (opens in a new tab)