Loading vulnerability…
CVE-2026-1180 is a blind server-side request forgery vulnerability in Keycloak’s OpenID Connect Dynamic Client Registration flow when client authentication uses private_key_jwt. The flaw arises because a registering client can supply an arbitrary jwks_uri, which Keycloak retrieves without adequately validating or restricting the destination. By causing the server to fetch attacker-selected URIs, an attacker can induce outbound HTTP requests from the Keycloak server to internal or otherwise restricted network locations. This behavior can be used to probe internal services and access cloud metadata endpoints, creating an information disclosure and internal reconnaissance risk.
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.
3 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.