Home › Vulnerabilities

Keycloak Flaw CVE-2026-117691: Update Now

Published November 5, 2026 · Last updated November 5, 2026

CVE Critical Patch

The short version: CVE-2026-117691 is a critical-severity security flaw in Keycloak. The National Vulnerability Database (NVD) published it on November 5, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 5, 2026, CISA had not added CVE-2026-117691 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-117691

The record was filed by redhat.com. In its own words: "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."

Why Keycloak admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on redhat.com rated CVE-2026-117691 9.1 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Keycloak running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

The type of bug behind CVE-2026-117691

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-347, Improper Verification of Cryptographic Signature. MITRE describes this class of bug as follows: "The product does not verify, or incorrectly verifies, the cryptographic signature for data."

Vendor remediation for CVE-2026-117691

The vendor advisory remediation for operators of Keycloak, quoted for this page, is: "Upgrade Keycloak to version 26.8.2 or later (released Nov 5, 2026), which fixes the SAML redirect binding signature bypass; if you use SAML identity brokering with HTTP-Redirect binding, treat updating as urgent, then review recent federated sign-in logs for unexpected logins and rotate any sessions for affected realms. Keycloak lists the fix in its 26.8.2 release notes (GitHub keycloak/keycloak issue 54714)."

What to do about it

  • Update now: Upgrade Keycloak to version 26.8.2 or later (released Nov 5, 2026), which fixes the SAML redirect binding signature bypass; if you use SAML identity brokering with HTTP-Redirect binding, treat updating as urgent, then review recent federated sign-in logs for unexpected logins and rotate any sessions for affected realms. Keycloak lists the fix in its 26.8.2 release notes (GitHub keycloak/keycloak issue 54714).
  • Who should act: IT teams, managed service providers, and developers who run or ship Keycloak. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Keycloak (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 5, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-117691. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-117691 record details from CISA and NVD

  • Attack complexity for CVE-2026-117691: low
  • CVE-2026-117691 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-117691: exploitability 3.9, impact 5.2.
  • Who mapped the weakness type: the address listed on redhat.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 5, 2026: NVD publishes CVE-2026-117691.
  • November 5, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-117691 is not listed.
  • November 5, 2026: most recent NVD update (record status: Awaiting Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.