CVE-2026-93998

Keycloak-core: keycloak-core: saml adapter does not bind signed assertions to the configured identity provider issuer

  • High 7.4

Description

A flaw was found in the SAML adapter component of Keycloak, which is used to secure applications with SAML-based authentication. The adapter fails to verify that the issuer of a signed SAML assertion matches the expected identity provider configured for the application. If multiple identity providers share the same trusted signing key, an attacker who controls one of those providers can create a validly signed assertion to log into the application as any user, potentially gaining full administrative control.

Key facts

Published
5 Nov 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.262% likely to be exploited in the next 30 days, higher than 18.093% 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.4CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • 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 enforce strict verification of the SAML assertion Issuer attribute against the configured identity provider entity ID in the Keycloak SAML adapter: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the corresponding fixed Red Hat builds), which verify that the Issuer attribute in the received SAML response and assertion strictly matches the configured identity provider entity ID, closing all 2 injection vectors (cross-tenant SAML assertion injection, shared-key sibling issuer assertion forging). Until patched, this is a concern on Applications secured using the Keycloak SAML adapter where signing keys are shared across multiple identity providers or tenants, so Ensure signing keys are strictly isolated per identity provider and never shared across multiple issuers or tenants. These controls limit blast radius and contain exploitCNA 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.

CNA context is abbreviated; consult the original record for the complete statements.

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.4.17
  • Default status: 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 build of Keycloak 26.6.8
  • Default status: 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 AMQ Broker 7
  • Default status: unaffected
Red HatRed Hat Fuse 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 8
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack
  • Default status: unaffected
Red HatRed Hat Satellite 6
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: unaffected

Timeline

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

Weakness

References