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.
Published: 2026-11-05
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor 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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 06 Nov 2026 17:30:00 +0000

Type Values Removed Values Added
References

Fri, 06 Nov 2026 10:30:00 +0000

Type Values Removed Values Added
CPEs cpe:/a:redhat:build_keycloak: cpe:/a:redhat:build_keycloak:26.6::el9
References

Fri, 06 Nov 2026 00:30:00 +0000

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Build Of Keycloak 26.4
Redhat build Of Keycloak
Redhat single Sign-on
Vendors & Products Red Hat
Red Hat red Hat Build Of Keycloak 26.4
Redhat build Of Keycloak
Redhat single Sign-on

Fri, 06 Nov 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Important


Thu, 05 Nov 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title Keycloak-services: keycloak-services: account takeover via stale sso_auth note in organization identity-first login
First Time appeared Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
Weaknesses CWE-305
CPEs cpe:/a:redhat:build_keycloak:
cpe:/a:redhat:red_hat_single_sign_on:7
Vendors & Products Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Red Hat Red Hat Build Of Keycloak 26.4
Redhat Build Keycloak Build Of Keycloak Red Hat Single Sign On Single Sign-on
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-06T19:55:23.323Z

Reserved: 2026-10-19T10:15:42.791Z

Link: CVE-2026-112208

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-05T17:17:38.283

Modified: 2026-11-06T18:17:45.320

Link: CVE-2026-112208

cve-icon Redhat

Severity : Important

Publid Date: 2026-11-05T00:00:00Z

Links: CVE-2026-112208 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T00:15:14Z

Weaknesses