CVE-2026-82965
Keycloak-services: keycloak-services: unauthenticated denial of service via saml soap endpoint unbounded xml parsing
What happened?
A flaw was found in the SAML implementation of Keycloak, an open-source identity and access management solution. The SAML Artifact Resolution and ECP SOAP endpoints do not properly limit the size or complexity of incoming XML requests. An unauthenticated remote attacker can exploit this by sending specially crafted, large XML messages that cause the server to consume excessive memory. This leads to the application running out of memory and crashing, resulting in a denial of service for all users.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| keycloak-rhel9-containerRed Hat | unaffected: 26.4-29 to < * | See vendor advisory |
| keycloak-rhel9-operator-bundle-containerRed Hat | unaffected: 26.4.17-2 to < * | See vendor advisory |
| keycloak-rhel9-operator-containerRed Hat | unaffected: 26.4-30 to < * | See vendor advisory |
| keycloak/rhbk-openshift-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| keycloak-servicesRed Hat | Default status: unaffected | See vendor advisory |
| rhbk/keycloak-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| keycloak-servicesRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.