Descrizione

Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.

Testo originale del record CVE (in inglese).

Come correggere

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

Versioni da aggiornare

  • Red Hat Red Hat build of Keycloak 26.4: versione corretta 26.4.17-2 (o successiva).
  • Red Hat Red Hat build of Keycloak 26.4: versione corretta 26.4-29 (o successiva).
  • Red Hat Red Hat build of Keycloak 26.4: versione corretta 26.4-30 (o successiva).
  • 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 validate protocol mapper claim.name configurations during Dynamic Client Registration to deny mapping to reserved identity claims: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the corresponding fixed Red Hat builds), which validate and reject protocol mapper configurations in Dynamic Client Registration that assign reserved claims to claim.name, closing all 2 injection vectors (Dynamic Client Registration protocol mapper configuration mapping user profile attributes to the sub claim, Dynamic Client Registration protocol mapper configuration mapping user profile attributes to the aud claim). Until patched, this is a concern on Keycloak deployments enabling Dynamic Client Registration where users possess an Initial Access Token and editable realm profile attributes, so restrict issuance of Initial Access Tokens, monitor new…

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.4 — 26.4.17-2
Red Hat Red Hat build of Keycloak 26.4 — 26.4-29
Red Hat Red Hat build of Keycloak 26.4 — 26.4-30
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