CVE-2026-4366 is a server-side request forgery vulnerability in Keycloak, an identity and access management platform. The flaw stems from improper handling of HTTP redirects during certain client configuration requests, where the server follows redirects to attacker-influenced destinations without adequately restricting the target. By abusing this behavior, an attacker can induce the Keycloak server to issue unintended outbound requests to internal or otherwise restricted resources. Because the issue is described as blind SSRF, exploitation may not return full response content directly to the attacker, but it can still be used to reach sensitive internal services, including cloud metadata endpoints, and to probe internal network reachability.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.