CVE-2026-112208
Keycloak-services: keycloak-services: account takeover via stale sso_auth note in organization identity-first login
A flaw was found in the Organization identity-first login flow of the Keycloak authentication server. Keycloak is an open-source identity and access management solution used to secure modern applications and services. The issue occurs when an attacker who belongs to multiple organizations initiates a login and then switches to a registration or password reset path. During this process, a flag indicating a successful login is not properly cleared when the user is removed from the session. An attacker can then provide a victim's username, and the system incorrectly treats the stale flag as proof of the victim's identity. This allows the attacker to bypass authentication and gain full access to the victim's account and connected applications.
Fixes and workarounds
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to ensure the SSO_AUTH re-authentication note is cleared from the authentication session whenever a flow transition strips the authenticated user: upgrade to Red Hat build of Keycloak 26.6.8 (or the fixed Rhbk/Keycloak Rhel/Keycloak Services builds), which clears the lingering SSO_AUTH re-authentication note from the authentication session during login flow transitions such as registration or credential reset, closing all 2 injection vectors (transition to credential reset flow, transition to registration flow). Until patched, this is a concern on Keycloak deployments with the Organization feature enabled and users holding credentials in multiple organizations, so Disable the Organization feature or ensure users cannot hold memberships across multiple organizations. These controls limit blast radius and contain exploitation, but they do not fix the underlying stale authentication state flag defect — apply the upstream patch to fully remediate.
Source: CNA: redhatAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Red Hat build of Keycloak 26.6 Red Hat rhbk/keycloak-operator-bundle
https://catalog.redhat.com/software/containers/ |
≥ 26.6.8-2; < * (unaffected, rpm)
Other versions: affected |
CNA: redhat |
| Red Hat build of Keycloak 26.6 Red Hat rhbk/keycloak-rhel9
https://catalog.redhat.com/software/containers/ |
≥ 26.6-24; < * (unaffected, rpm)
Other versions: affected |
CNA: redhat |
| Red Hat build of Keycloak 26.6 Red Hat rhbk/keycloak-rhel9-operator
https://catalog.redhat.com/software/containers/ |
≥ 26.6-24; < * (unaffected, rpm)
Other versions: affected |
CNA: redhat |
| Red Hat build of Keycloak 26.6.8 Red Hat keycloak-services
https://access.redhat.com/downloads/content/package-browser/ |
Range not reported
Other versions: unaffected |
CNA: redhat |
| Red Hat build of Keycloak 26.6.8 Red Hat rhbk/keycloak-rhel9
https://access.redhat.com/downloads/content/package-browser/ |
Range not reported
Other versions: unaffected |
CNA: redhat |
| Red Hat Single Sign-On 7 Red Hat keycloak-services
https://access.redhat.com/downloads/content/package-browser/ |
Range not reported
Other versions: unaffected |
CNA: redhat |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA: redhat |
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://access.redhat.com/errata/RHSA-2026:95761CNA: redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:95762CNA: redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-112208CNA: redhat · vdb-entry, x_refsource_REDHAT
- https://bugzilla.redhat.com/show_bug.cgi?id=2555473CNA: redhat · issue-tracking, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:95761[email protected]
- https://access.redhat.com/security/cve/CVE-2026-112208[email protected]
- https://bugzilla.redhat.com/show_bug.cgi?id=2555473[email protected]
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.