Skip to content
Fencer Vulns
high 8.8

CVE-2026-97175 json

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

published 2026-11-05 3 d ago modified 2026-11-06 2 d ago also EUVD-2026-117611

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-97175 updated cvss 8.8

keycloak-services: keycloak-services: Unverified IdP email auto-linking enables account takeover

  • Red Hat build of Keycloak 26.4.17
    fixed: vendor fix RHSA-2026:95759
  • Red Hat build of Keycloak 26.6.8
    fixed: vendor fix RHSA-2026:95761
  • Red Hat Single Sign-On 7 keycloak-services 18.0.19.redhat-00002
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Red Hat Red Hat build of Keycloak 26.4.17
  • Red Hat Red Hat build of Keycloak 26.6.8
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.