Descrizione
A flaw was found in the idp-auto-link authenticator of the keycloak-services component, which handles user identity federation. The issue occurs when Keycloak automatically links an incoming identity from an external provider to an existing local account based on an email address without verifying if the provider has validated that email. This can allow an attacker to take over a victim's account by using a matching unverified email address at a brokered provider.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 8.8, EPSS 0.4% (percentile 30).
Versioni da aggiornare
Il record non riporta ancora i prodotti e le versioni corrette (analisi NVD in corso). Consultare l'advisory del vendor nei riferimenti.
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 require verification of the email verified claim before linking brokered identities to local accounts in the idp-auto-link authenticator: upgrade to Red Hat build of Keycloak 26.4.17 (or the fixed Rhbk/Keycloak Rhel/Keycloak Services builds), which verify the email verified claim before automatically linking an incoming brokered identity to an existing local account, closing federated identity login using unverified matching email address. Until patched, this is a concern on Keycloak deployments configured with the idp-auto-link authenticator in the first-broker-login flow, so audit brokered external identity providers to ensure they enforce email verification, or avoid using external providers that permit arbitrary unverified email addresses matching existing local accounts. As a compensating measure, Enforce multi-factor…
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Non esporre l'interfaccia di gestione su Internet: consentire l'accesso solo da reti fidate e verificare la presenza di account, sessioni o chiavi non autorizzate.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Riferimenti
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:95759
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:95760
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:95761
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:95762
- Riferimentohttps://access.redhat.com/security/cve/CVE-2026-97175