Loading vulnerability…
Keycloak exposes distinguishable SOAP faultstrings through its SAML Enhanced Client or Proxy (ECP) endpoint when requests use varying client IDs. A remote unauthenticated attacker can submit specially crafted SOAP requests and compare the returned errors to infer a referenced client's protocol type.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This 13-file Python security-research repository centers on CVE-2026-9794: an unauthenticated Keycloak SAML ECP SOAP faultstring oracle. The primary executable, ecp_enum.py, sends a crafted SOAP/SAML AuthnRequest to POST /realms/{realm}/protocol/saml, inserts each candidate client ID as the SAML issuer, and classifies response fault strings. It supports a built-in or external wordlist, configurable target host/realm/concurrency, and identifies client existence, OIDC versus SAML behavior, disabled/bearer-only/standard-flow-disabled states, signature requirements, and ECP eligibility. It also recognizes realm-not-found and HTTPS/realm-disabled responses. The documented affected range is Keycloak 2.0 through 26.6.1, with the README stating the enumeration issue was fixed in 26.6.3. The remaining three Python files are local validation utilities rather than parts of the primary unauthenticated exploit: jwks_ssrf_test.py and ssrf_tests.py create an administrator-controlled client and check for outbound SSRF through jwks.url and OAuth request_uri handling; xxe_confirm.py probes SAML SOAP parsing for OOB XXE, file reads, and entity expansion. The accompanying Markdown reports document Keycloak attack surface mapping, source audits, observed fault behavior, disclosure material, and a reproducible Docker lab. The reports state that request_uri SSRF affected 26.0.8 but was no longer triggered in 26.6.1; JWKS SSRF requires privileged client registration; and tested DOCTYPE XXE was blocked by saaj-impl 2.0.1. The repository is therefore a functional reconnaissance exploit with supplemental, environment-specific SSRF and parser-security test code, not an authentication-bypass or remote-code-execution exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.