Keycloak. This vulnerability · CWE-347
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 20 Nov 2026, 01:38 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Build of Keycloakkeycloak-saml-core | Affected– | Fixed in– |
| Red Hat Build of Keycloakrhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 | Affected– | Fixed in– |
| Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 | Affected– | Fixed in– |
| Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 | Affected– | Fixed in– |
| Red Hat JBoss Enterprise Application Platform 8keycloak-saml-core | Affected– | Fixed in– |
AI-suggested
Until a fix is available, restrict authenticated user privileges to limit exposure and monitor for suspicious session termination activity.
Description
A vulnerability in Keycloak allows an authenticated remote attacker to cause denial of service by terminating active sessions of arbitrary users. This occurs because Keycloak improperly processes SAML logout requests that lack a root signature, accepting any request containing a validly signed assertion regardless of its context. The attacker can embed a signed assertion into an unsigned logout request for another user, causing Keycloak to accept the forged request and terminate the victim's session.