CVE-2026-97175

Keycloak-services: keycloak-services: unverified idp email auto-linking enables account takeover

Published Nov 5, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
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.

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 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 authentication on target Keycloak accounts to prevent attackers from completing account takeovers even if the federated identity is automatically linked. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper authentication defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-801 Multi-Factor Authentication (MFA) (medium)

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:/a:redhat:build_keycloak:26.4::el9
References
Type Values Removed Values Added
CPEs cpe:/a:redhat:build_keycloak: cpe:/a:redhat:build_keycloak:26.6::el9
References
Type Values Removed Values Added
Description 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.
Title Keycloak-services: keycloak-services: unverified idp email auto-linking enables account takeover
First Time appeared Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
Weaknesses CWE-287
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.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 9, 2026, 10:25 PM
Reserved
Sep 24, 2026, 5:31 AM
Status
Awaiting Analysis
Published
Nov 5, 2026, 6:17 PM
Modified
Nov 9, 2026, 11:17 PM
Severity
Important
Public date
Nov 5, 2026, 12:00 AM