Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
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 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 Keycloak when worker threads hang and Implement rate limiting and connection throttling on unauthenticated HTTP requests targeting Keycloak SAML endpoints to mitigate thread exhaustion. These controls limit blast radius and contain exploitation, but they do not fix the underlying infinite-loop XML parsing defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1204 Service Watchdog and Automatic Restart (systemd WatchdogSec/Restart) (medium)
Fri, 06 Nov 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 06 Nov 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:build_keycloak:26.4::el9 cpe:/a:redhat:build_keycloak:26.6::el9 |
|
| References |
|
Fri, 06 Nov 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 05 Nov 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Red Hat
Red Hat red Hat Build Of Keycloak 26.4 Redhat build Of Keycloak Redhat single Sign-on |
|
| Vendors & Products |
Red Hat
Red Hat red Hat Build Of Keycloak 26.4 Redhat build Of Keycloak Redhat single Sign-on |
Thu, 05 Nov 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Keycloak-services: keycloak-services: unauthenticated cpu exhaustion via saml 1.1 keyinfo infinite loop | |
| First Time appeared |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
| Weaknesses | CWE-835 | |
| CPEs | cpe:/a:redhat:build_keycloak: cpe:/a:redhat:red_hat_single_sign_on:7 |
|
| Vendors & Products |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-06T19:55:17.180Z
Reserved: 2026-10-08T12:39:57.410Z
Link: CVE-2026-107602
No data.
Status : Awaiting Analysis
Published: 2026-11-05T17:17:35.117
Modified: 2026-11-06T17:17:12.970
Link: CVE-2026-107602
OpenCVE Enrichment
Updated: 2026-11-05T23:15:11Z