A parser loop can consume CPU
CVE-2026-107602 affects SAML 1.1 XML parsing in Keycloak. Red Hat says unexpected child elements in a token’s key information section can leave the parser in an infinite loop. An unauthenticated remote request can consume CPU and worker threads and make the service unavailable.
The issue is important for deployments that expose SAML endpoints to untrusted networks. Red Hat’s CVE record describes the issue and affected product status; product builds and release fixes can vary. Use the advisory for the exact Keycloak distribution that you run.
Map identity endpoints and dependencies
List Keycloak realms that accept SAML, the public and internal URLs for their endpoints, and the applications that depend on them. Confirm which nodes and product builds are exposed. Check logs and service metrics for unusual CPU use or repeated parsing failures.
Do not copy mitigation text from third-party aggregators without checking the product vendor. Follow the official Red Hat or upstream Keycloak notice for the exact fixed release and supported action.
Apply the vendor fix and validate sign-in
Update the relevant Keycloak distribution to a release confirmed as fixed by its supplier. Test SAML login, logout and identity-provider integration across the affected realms. Confirm that all cluster members run the intended build.
If a service shows unexplained CPU exhaustion or authentication failures, preserve logs and follow your incident process. Monitor SAML endpoint health after the change and make sure application owners know the maintenance window.
