Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

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

CVE-2026-117691 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
9.1 (NetApp), 9.1 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N · base score 9.1, scored by redhatAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-347 Improper Verification of Cryptographic Signature
EPSS
0.28% chance of exploitation in the next 30 days (20th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: total. CISA, .
Fixed releases
  • Red Hat: rhbk/keycloak-rhel9, rhbk/keycloak-rhel9-operator:26.6-26, rhbk/keycloak-operator-bundle:26.6.9-1, rhbk/keycloak-rhel9:26.6-25, RHSA-2026:96039
Vendor advisories
2 from NetApp, Red Hat
Assigned by
redhat (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-117691; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.

Text from the CVE.org record (redhat).

How do I fix CVE-2026-117691?

Upgrade to a fixed release named by the vendor:

  • Red Hat: rhbk/keycloak-rhel9, rhbk/keycloak-rhel9-operator:26.6-26, rhbk/keycloak-operator-bundle:26.6.9-1, rhbk/keycloak-rhel9:26.6-25, RHSA-2026:96039
  • Workaround: 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 blast radius and contain exploitation, but they do not fix the underlying SAML parameter parsing discrepancy signature bypass — apply the upstream patch to fully remediate. (CVE.org record)

Vendor advisories for CVE-2026-117691

NetApp

1 advisory
  • Advisory severityCritical9.1

    Critical [CVE-2026-117691] Keycloak Vulnerability in NetApp Products

    NTAP-20261118-0012Source published Source updated

    Keycloak versions prior to 26.8.2 are susceptible to a vulnerability which when successfully exploited could allow an attacker to 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. Successful exploitation of this vulnerability could lead to disclosure of sensitive information or addition or modification of data. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 26.8.2
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityCritical9.1

    Critical [CVE-2026-117691] SAML redirect binding signature bypass via percent-encoded parameter names

    CVE-2026-117691Source published Source updated

    SAML redirect binding signature bypass via percent-encoded parameter names. Red Hat rates this important (CVSS 9.1). Weakness: CWE-347. Red Hat lists fixing advisory RHSA-2026:96039 with package rhbk/keycloak-rhel9, keycloak-services, rhbk/keycloak-rhel9-operator:26.6-26, rhbk/keycloak-operator-bundle:26.6.9-1. Affected product named by the advisory: Red Hat build of Keycloak 26.6.

    Related products — impact not confirmed
    • Red Hat build of Keycloak 26.6
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • rhbk/keycloak-rhel9
    • rhbk/keycloak-rhel9-operator:26.6-26
    • rhbk/keycloak-operator-bundle:26.6.9-1
    • rhbk/keycloak-rhel9:26.6-25

    1 more entries in the full advisory.

    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Workarounds
    • 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.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp