CVE-2026-2092: Red Hat build of Keycloak 26.2 · Improper Validation of Specified Type of Input
Affects Red Hat build of Keycloak 26.2Source CVE Database V5
Not known to be exploited · CVSS 7.7 High : upgrade Red Hat build of Keycloak 26.2 to 26.2.14 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.2.14
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Mar 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 29 Oct 2026.
What to do
Upgrade org.keycloak/keycloak to 26.2.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.keycloak/keycloakpkg:maven/org.keycloak/keycloakOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Red Hat has released version 26.2.14 of the Red Hat build of Keycloak which addresses this vulnerability. Users should upgrade to version 26.2.14 or later to remediate the issue. Before applying the update, it is recommended to back up existing installations, including applications, configuration files, and databases. No other mitigations are specified in the vendor advisory. Patch status is confirmed as fixed in 26.2.14.
Description
A flaw was found in Keycloak. Keycloak's Security Assertion Markup Language (SAML) broker endpoint does not properly validate encrypted assertions when the overall SAML response is not signed. An attacker with a valid signed SAML assertion can exploit this by crafting a malicious SAML response. This allows the attacker to inject an encrypted assertion for an arbitrary principal, leading to unauthorized access and potential information disclosure.
References
- access.redhat.com/errata/RHSA-2026:3925 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3926 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3947 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3948 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-2092 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2437296 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2092.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:76132 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:76134 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:76129 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:76130 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:76128 (opens in a new tab)