CVE-2026-2092: Keycloak improper validation of encrypted SAML assertions

CVE-2026-2092 · Severity: high · CVSS 7.7 · Published 2026-03-18

Keycloak, an open-source identity and access management solution, contains a vulnerability in how it handles SAML login requests. An attacker with basic user access can bypass security checks to impersonate other users or access sensitive information. This could lead to unauthorized access to corporate applications and potential data breaches.

Technologies: Keycloak, org.keycloak:keycloak-services (Maven), Red Hat build of Keycloak. Vendors: Keycloak, Maven, Red Hat.

Quick answers

Is CVE-2026-2092 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-2092 being exploited in the wild.
How severe is CVE-2026-2092?
High severity, with a CVSS score of 7.7, published 18 March 2026.
Which products and versions are affected?
Keycloak < 26.2.14, >= 26.3.0 < 26.4.10, >= 26.5.0 < 26.5.5, <= 26.2.5, >= 26.3.0, <= 26.4.7, >= 26.5.0, < 26.5.5, versions prior to 26.2.14, 26.4.10; org.keycloak:keycloak-services (Maven) ECOSYSTEM:introduced=0,last_affected=26.2.5; Red Hat build of Keycloak 26.2.14, 26.4.10.
Is there a fix for CVE-2026-2092?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-2092 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-2092?
Check whether you run Keycloak, org.keycloak:keycloak-services (Maven) or Red Hat build of Keycloak at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in Keycloak's SAML broker endpoint arises from improper validation of encrypted assertions (CWE-1287) when the encompassing SAML response lacks a digital signature. An attacker possessing a valid signed SAML assertion can craft a malicious SAML response and inject an encrypted assertion for an arbitrary principal. This exploit requires network access and low-level privileges but can result in a scope change, allowing the attacker to gain unauthorized access and disclose sensitive information. The issue affects multiple version ranges including <= 26.2.5, 26.3.x, and 26.5.x. A fix is available in version 26.5.5 and via specific commits in the project repository.

Affected products

  • Keycloak Keycloak <= 26.2.5, >= 26.3.0, <= 26.4.7, >= 26.5.0, < 26.5.5

Identifiers

  • CVE-2026-2092
  • GHSA-794g-x443-36f7
  • GHSA-wmxr-6j5f-838p

Timeline

  • 2026-05-29: disclosed: Initial disclosure to Keycloak maintainers
  • 2026-07-02: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.