Skip to content
Fencer Vulns
medium 6.4

CVE-2026-82968 json

Keycloak-services: keycloak-services: cross-session email verification proof not bound to upstream identity for social providers

published 2026-09-02 2 mo ago modified 2026-11-06 3 d ago also EUVD-2026-69800

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

Summary

A flaw was found in the first-broker-login flow of the Keycloak identity management service. When a user links a social identity provider account to their local account, the verification proof generated is not strictly bound to the specific upstream identity being verified. This allows an attacker with a different account on the same social provider to intercept the process and link their own account to the victim's local profile, gaining unauthorized access.

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-82968 updated cvss 6.4

keycloak-services: keycloak-services: Cross-session email verification proof not bound to upstream identity for social providers

  • Red Hat Single Sign-On 7 keycloak-services 18.0.3.redhat-00001
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Keycloak 26.6.8
    fixed: vendor fix RHSA-2026:95761

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

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

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

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.