CVE-2026-93998 json
Keycloak-core: keycloak-core: saml adapter does not bind signed assertions to the configured identity provider issuer
published 2026-11-05 3 d ago modified 2026-11-06 2 d ago also EUVD-2026-117608
- cvss
- 7.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 18%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Red Hat Red Hat build of Keycloak 26.4 26.4-29, 26.4-30, 26.4.17-2
- Red Hat Red Hat build of Keycloak 26.6 26.6-24, 26.6.8-2
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-93998 updated cvss 7.4
keycloak-core: keycloak-core: SAML adapter does not bind signed assertions to the configured identity provider issuer
-
Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-29, rhbk/keycloak-rhel9-operator 26.4-30, rhbk/keycloak-operator-bundle 26.4.17-2fixed: vendor fix RHSA-2026:95760
-
Red Hat build of Keycloak 26.4.17fixed: vendor fix RHSA-2026:95759
-
Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-24, rhbk/keycloak-rhel9-operator 26.6-24, rhbk/keycloak-operator-bundle 26.6.8-2fixed: vendor fix RHSA-2026:95762
-
Red Hat build of Keycloak 26.6.8fixed: vendor fix RHSA-2026:95761
-
Red Hat AMQ Broker 7 keycloak-core 24.0.10.redhat-00003 Red Hat Fuse 7 keycloak-core 24.0.10.redhat-00003 Red Hat JBoss Enterprise Application Platform 7 jboss-eap-7/eap74-els-openjdk8-openshift-rhel8, jboss-eap-7/eap74-els-openjdk11-openshift-rhel8, jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 Red Hat JBoss Enterprise Application Platform 8 keycloak-core 24.0.10.redhat-00003 Red Hat JBoss Enterprise Application Platform Expansion Pack keycloak-core 24.0.10.redhat-00003 Red Hat Satellite 6 candlepin, candlepin-selinuxnot affected: vulnerable code not present
+1 more productsfewer
Red Hat Single Sign-On 7 keycloak-core 24.0.10.redhat-00003
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
- 3 d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- Red Hat Red Hat build of Keycloak 26.4
- Red Hat Red Hat build of Keycloak 26.4.17
- Red Hat Red Hat build of Keycloak 26.6
- Red Hat Red Hat build of Keycloak 26.6.8
- Red Hat Red Hat AMQ Broker 7
- Red Hat Red Hat Fuse 7
- Red Hat Red Hat JBoss Enterprise Application Platform 7
- Red Hat Red Hat JBoss Enterprise Application Platform 8
- Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
- Red Hat Red Hat Satellite 6
- Red Hat Red Hat Single Sign-On 7
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
access.redhat.com
/errata/RHSA-2026:95759
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:95760
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:95761
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:95762
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-93998
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2537164
issue-tracking
Sources
- CVE List CVE-2026-93998
- NVD CVE-2026-93998
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.