CVE-2026-97175High· 8.8▾ TwilightA 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 exist…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
keycloak-services (all versions)rhbk/keycloak-rhel9 (all versions)keycloak-servicesRefer to the linked advisories for vendor-supplied fixes and affected version ranges.
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.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-97847High· 7.1Keycloak-services: keycloak-services: client manager can substitute sessionless token principal via hardcoded-claim mappers to obtain realm administrator authority
CVE-2026-118959Medium· 5.4Keycloak-services: keycloak-services: required actions bypassed via kc_action parameter
CVE-2026-114438Medium· 4.2Keycloak-services: keycloak-services: required otp enrollment bypassed via update user locale required action ordering
CVE-2026-109082Medium· 6.8A flaw was found in the Client-Initiated Backchannel Authentication CIBA implementation within the keycloak-services component of Keycloak
CVE-2026-105305Medium· 5.4A flaw was found in the OIDC implementation of Keycloak, specifically within the Device Authorization Grant flow
CVE-2026-97846Medium· 6.8Keycloak provides a feature called mTLS holder-of-key binding which ensures that a token can only be used by the client that originally requested it by binding it to their digital certificate