CVE-2026-103112

Keycloak-services: keycloak-services: account takeover via authentication race using reset-credentials path

  • High 7.5

Description

A flaw was found in the authentication session handling of the keycloak-services component in Keycloak. The issue occurs because the system fails to verify if an authenticator is valid for the current authentication flow when switching between the standard authentication path and the reset credentials path. An authenticated attacker can exploit this by triggering a race condition during the credential reset process to associate their successful authentication state with another user's session. This can result in the attacker gaining full access to the victim's account and changing their password.

Key facts

Published
5 Nov 2026
Last changed
10 Nov 2026
Assigned by
redhat
EPSS
0.394% likely to be exploited in the next 30 days, higher than 34.178% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

What to do

  • --- 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 validate that the requested authenticator ID belongs to the active execution flow when switching between authenticate and reset-credentials endpoints in keycloak-services: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the fixed Rhbk/Keycloak Rhel/Keycloak Services builds), which validate that the requested authenticator ID is present in the active execution flow when switching between authenticate and reset-credentials endpoints, closing concurrent race condition between reset-credentials and authenticate endpoints during flow switching. Until patched, this is a concern on Keycloak deployments with Forgot Credentials enabled and users without two-factor authentication, so Enforce two-factor authentication for all realm users or disable the Forgot Credentials feature to prevent cross-flow identity binding. These controls limit blast radius and contain exploitation, but they do not fix the underlying authentication race condition defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-801 Multi-Factor Authentication (MFA) (high)CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4.17-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-29 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-30 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6.8-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: affected

Timeline

  1. 29 Sep 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References