CVE-2026-107602

Fixes and workarounds

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)