CVE-2026-117691

Keycloak-services: keycloak-services: saml redirect binding signature bypass via percent-encoded parameter names

  • Critical 9.1

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.

Key facts

Published
5 Nov 2026
Last changed
7 Nov 2026
Assigned by
redhat
EPSS
0.282% likely to be exploited in the next 30 days, higher than 20.979% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.1CVSS 3.1, Criticalfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to align query parameter parsing between signature verification and request processing in Keycloak's SAML HTTP-Redirect binding so percent-encoded parameter names cannot evade signature checks: upgrade to the fixed Rhbk/Keycloak Rhel/Keycloak Services builds, which eliminates the parsing discrepancy between raw query parameter signature verification and decoded parameter processing in the SAML redirect binding, closing crafted HTTP GET request containing a percent-encoded unsigned SAML parameter placed before a legitimately signed parameter. Until patched, this is a concern on Keycloak instances configured to use SAML HTTP-Redirect binding for federated identity, so Audit and restrict account registration on external Identity Providers to prevent attackers from capturing legitimately signed redirect-binding messages. These controls limit CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6.9-1 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-25 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-26 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6.9
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.9
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: unaffected

Timeline

  1. 26 Oct 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References