major vulnerability· requires attention

Affects Keycloak (widely used SSO/IDM); vulnerability enables federated account takeover, a high-impact authentication failure likely to hit many orgs.

Applications

CVE-2026-117691

9.1

Critical

EPSS n/aPatch available

Keycloak SAML redirect parsing flaw allows unsigned SAML to impersonate users.

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

No EPSS score yet

Published 5 Nov 2026Analysed here 5 Nov 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-117691 being exploited?

Not confirmed. CVE-2026-117691 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-117691?

CVE-2026-117691 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-117691?

Yes. A fix has been recorded for CVE-2026-117691. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-117691 affect?

CVE-2026-117691 affects Keycloak (SAML HTTP-Redirect binding). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-117691?

Apply vendor patch immediately; disable HTTP-Redirect SAML or enforce strict decoding if patch delayed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

Keycloak (SAML HTTP-Redirect binding)

impact

Percent-encoded SAML params bypass signature checks, enabling attackers to perform federated account takeover and gain full access.

action required

Immediate action required

cisa ssvc

exploitation: none
automatable: yes
technical impact: total

Assessed by CISA 5 Nov 2026 (SSVC 2.0.3).

timeline

5 Nov 2026Published
5 Nov 2026CISA SSVC assessment: exploitation none · same day later
5 Nov 2026CVE record last updated · same day later
5 Nov 2026Analysed by vulneraibility.com · same day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 links

Linkaccess.redhat.com /security/cve/CVE-2026-117691
Linkbugzilla.redhat.com /show_bug.cgi?id=2561977

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free