Descrizione

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.

Testo originale del record CVE (in inglese).

Come correggere

Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 8.1, EPSS 0.5% (percentile 39).

Versioni da aggiornare

  • Red Hat Red Hat build of Keycloak 26.6: versione corretta 26.6.8-2 (o successiva).
  • Red Hat Red Hat build of Keycloak 26.6: versione corretta 26.6-24 (o successiva).

Indicazioni del vendor

Workaround (testo originale del vendor):

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…

Mitigazioni temporanee

Da applicare solo se non è possibile aggiornare subito:

  • Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.

Verifica

  1. Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
  2. Confrontare la versione installata con quelle indicate sopra.
  3. Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
  4. Ripetere la scansione per confermare la correzione.

Configurazioni interessate

VendorProdottoVersioni vulnerabiliCorretta in
Red Hat Red Hat build of Keycloak 26.6 — 26.6.8-2
Red Hat Red Hat build of Keycloak 26.6 — 26.6-24

Riferimenti