Loading vulnerability…
CVE-2026-4634 is an application-level denial-of-service vulnerability in Keycloak. An unauthenticated attacker can trigger the flaw by sending a specially crafted POST request to the OpenID Connect token endpoint containing an excessively long scope parameter. Processing of the oversized scope value causes excessive server-side work and prolonged request handling, leading to high resource consumption in the Keycloak service. The issue affects Keycloak’s handling of OIDC scope parameters rather than requiring prior authentication or privileged access.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Keycloak denial-of-service vulnerability mentioned only as part of vendor security history.
A Keycloak application-level denial-of-service vulnerability via the scope parameter, mentioned only as part of vendor security history.
A denial-of-service vulnerability in Keycloak caused by excessive processing of OpenID Connect scope parameters.
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.