Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-93998

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

High7.4EPSS 0.26%
Published
Updated
Reserved
Assigned by
redhat

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.

Timeline

  1. ID reserved

    By redhat

  2. · 47 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-93998, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1High7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Awaiting Analysis3.1High7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.4.

Weakness

Affected products

What to do

Workaround: 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 exploitation, but they do not fix the underlying missing SAML issuer validation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93998 badge
[![CVE-2026-93998](https://trackcve.app/badge/CVE-2026-93998.svg)](https://trackcve.app/cve/CVE-2026-93998)

Record last updated .