CVE-2026-7307: Keycloak: keycloak: denial of service via specially crafted saml input
A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial of Service (DoS) where the server becomes unavailable.
Security readout for executives and security teams
Plain-English summary
CVE-2026-7307 is a denial-of-service flaw in Red Hat build of Keycloak. An unauthenticated remote actor can send specially crafted SAML XML that drives high CPU use and worker thread starvation, making authentication services unavailable.
Executive priority
Treat as high priority for organizations relying on Keycloak SAML login. The primary business risk is authentication outage, which can block workforce, customer, or partner access to dependent applications.
Technical view
The issue affects SAML endpoint processing in Red Hat build of Keycloak 26.2 and 26.4 packages listed by Red Hat. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges, no user interaction, and availability impact only.
Likely exposure
Exposure is most likely where Red Hat build of Keycloak 26.2 or 26.4 has reachable SAML endpoints. The source bundle identifies specific rhbk/keycloak-rhel9, operator, and operator-bundle package versions as affected.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. The described attack is remote and unauthenticated, but sources only support denial of service, not data theft or privilege escalation.
Researcher notes
Evidence supports a SAML XML parsing or processing DoS mapped to CWE-1286. Do not assume upstream Keycloak or non-Red Hat builds are affected unless vendor data confirms it.
Mitigation direction
Apply the relevant Red Hat advisory updates for affected RHBK 26.2 or 26.4 deployments.
Prioritize internet-facing or partner-facing SAML endpoints first.
Confirm package versions against Red Hat affected and unaffected status.
Monitor Keycloak CPU saturation, worker exhaustion, and authentication availability.
Check vendor guidance before applying compensating controls not named in sources.
Validation and detection
Inventory Red Hat build of Keycloak versions and package names.
Identify deployments with SAML endpoints reachable from untrusted networks.
Compare installed versions to Red Hat CVE and CSAF VEX records.
Review logs and metrics for unexplained CPU spikes or authentication outages.
Verify update status after applying Red Hat errata.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1286: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1286 · source CWE mapping
Improper Validation of Syntactic Correctness of Input
Improper Validation of Syntactic Correctness of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.