CVE-2026-107602
Keycloak-services: keycloak-services: unauthenticated cpu exhaustion via saml 1.1 keyinfo infinite loop
- High 7.5
Description
A flaw was found in the SAML 1.1 XML parsing logic of Keycloak, an open-source identity and access management solution. The issue occurs when the parser encounters unexpected elements within a security token's key information section, causing the processing thread to enter an infinite loop. An unauthenticated remote attacker could exploit this by sending specially crafted requests, leading to 100% CPU usage and a total denial of service that requires a server restart to resolve.
Key facts
- Published
- 5 Nov 2026
- Last changed
- 9 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.734% likely to be exploited in the next 30 days, higher than 54.982% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: yes; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.5CVSS 3.1, Highfrom the CNA (redhat)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 ensure the StAX-based XML parser in keycloak-saml-core advances the cursor or rejects unhandled child elements when parsing ds:KeyInfo in SAML 1.1 tokens: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the fixed Rhbk/Keycloak Rhel/Keycloak Services builds), which advances the cursor or rejects unexpected child elements within ds:KeyInfo rather than repeatedly peeking without advancing the parser, closing crafted SAML 1.1 request containing unexpected ds:KeyInfo child elements. Until patched, this is a concern on Keycloak deployments exposing unauthenticated SAML endpoints, so Restrict network access to Keycloak SAML endpoints such as /realms/{realm}/protocol/saml to trusted clients. As a compensating measure, Configure systemd service watchdogs (WatchdogSec and Restart) to monitor responsiveness and automatically restart KeycCNA 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.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4.17 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6.8 |
|
| Red Hat | Red Hat build of Keycloak 26.6.8 |
|
| Red Hat | Red Hat Single Sign-On 7 |
|
Timeline
- 7 Oct 2026 Reported to Red Hat.
- 5 Nov 2026 Made public.
- 5 Nov 2026 Published