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.
Affected products
redhat: build of keycloak
References10
- access.redhat.com/errata/RHSA-2026:3925 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3926 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3947 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3948 Vendor Advisory
- access.redhat.com/security/cve/CVE-2026-2092 Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2437296 Issue TrackingVendor Advisory
- access.redhat.com/errata/RHSA-2026:3925 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3926 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3947 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:3948 Vendor Advisory
Metrics
- CVSS 3.1
-
7.7
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L - EPSS — exploit probability
- 0% percentile: 33 · as of 12 November 2026
- CWE
- CWE-1287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.