CVE-2026-1180
Server-Side Request Forgery in Keycloak OpenID Dynamic Registration
Publication date: 2026-01-20
Last updated on: 2026-04-02
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| keycloak | keycloak | to 3.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1180 is a Blind Server-Side Request Forgery (SSRF) vulnerability in Keycloak's OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue occurs because Keycloak does not validate the jwks_uri parameter provided by clients during registration. This allows an attacker to specify a malicious jwks_uri that points to internal or restricted network resources. Keycloak then makes HTTP requests to these URIs, enabling attackers to probe internal services and cloud metadata endpoints without directly receiving the response, but by inferring information through timing and error analysis. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthenticated internal network reconnaissance and information disclosure. Attackers can coerce the Keycloak server into making HTTP requests to internal or restricted network resources, such as localhost services, private IP addresses, or cloud metadata endpoints. This can reveal the existence and accessibility of internal services, potentially exposing sensitive infrastructure details and increasing the risk of further attacks. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves monitoring for unusual or unauthorized client registrations that specify arbitrary or suspicious jwks_uri values, especially those pointing to internal IP addresses or cloud metadata endpoints. Since the vulnerability is a Blind SSRF, you can look for Keycloak server logs showing HTTP requests to unexpected internal resources triggered by client registrations using private_key_jwt authentication. Specific commands depend on your environment, but you might use network monitoring tools like tcpdump or Wireshark to capture outbound HTTP requests from the Keycloak server to internal IP ranges. For example, using tcpdump: `tcpdump -i <interface> host <keycloak-server-ip> and tcp port 80 or 443` to capture HTTP/HTTPS traffic, then filter for requests to internal IPs or metadata endpoints. Additionally, reviewing Keycloak logs for client registrations with unusual jwks_uri parameters can help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling anonymous or token-based client registrations if not required, and implementing validation or whitelisting of the jwks_uri parameter to prevent arbitrary URLs, especially those pointing to internal or cloud metadata endpoints. Applying available patches or updates from Keycloak that address this vulnerability is critical. Additionally, network-level controls such as firewall rules can block Keycloak servers from making HTTP requests to internal or sensitive network ranges to reduce the risk of SSRF exploitation. [1]