Description
A flaw was found in the SAML HTTP-Redirect binding implementation of Keycloak. The issue occurs because the server processes percent-encoded parameter names (like %53AMLResponse) while the signature verification logic only checks literal parameter names. An attacker can use this discrepancy to provide a crafted, unsigned SAML message that the server processes instead of a legitimately signed one, leading to full account takeover of federated users.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.6 | — | — |
| Red Hat | Red Hat build of Keycloak 26.6.9 | — | — |
| Red Hat | Red Hat Single Sign-On 7 | — | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
foxcornlab/keycloak-saml-scanner ★ 0 · Nov 7, 2026
Detection-only triage for CVE-2026-117691 (CVSS 9.1): Keycloak SAML HTTP-Redirect binding signature bypass, fixed in 26.8.2
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Advisories 1
- WID-SEC-2026-4375 Keycloak: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 11, 2026
References
- RHSA-2026:96039 vendor-advisory
- RHSA-2026:96040 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-117691 vdb-entry
- RHBZ#2561977 issue-tracking