PoC Monitor
← All CVEs
CVE-2026-93998published 5 Nov 2026 17:15 UTCData: JSON · API

Red Hat build of Keycloak 26.4

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.4high · scored by CNA · CWE-347
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Red Hat Red Hat build of Keycloak 26.4

    Fixed in 26.4.17-2

    Red Hat Red Hat build of Keycloak 26.4

      Fixed in 26.4-29

      Red Hat Red Hat build of Keycloak 26.4

        Fixed in 26.4-30

        Red Hat Red Hat build of Keycloak 26.6

          Fixed in 26.6.8-2

          Red Hat Red Hat build of Keycloak 26.6

            Fixed in 26.6-24

            Red Hat Red Hat build of Keycloak 26.6

              Fixed in 26.6-24

              Mitigation

              Upgrade Red Hat build of Keycloak 26.4 to 26.4.17-2 or later.

              Upgrade Red Hat build of Keycloak 26.4 to 26.4-29 or later.

              Upgrade Red Hat build of Keycloak 26.4 to 26.4-30 or later.

              Upgrade Red Hat build of Keycloak 26.6 to 26.6.8-2 or later.

              Upgrade Red Hat build of Keycloak 26.6 to 26.6-24 or later.

              Upgrade Red Hat build of Keycloak 26.6 to 26.6-24 or later.

              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

              1 more

              Timeline

              Days relative to CVE publication
              -2t=0+2+4+6+8CVE published5 Nov 2026 · t = 0

              No public PoC found yet; not in CISA KEV.

              PoC repositories

              Found on GitHub.

              No PoC repositories found yet.