Keycloak’s OpenID Connect Dynamic Client Registration feature affected by Server-Side Request Forgery (SSRF)
A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbitrary jwks_uri, which Keycloak then retrieves without validating the destination. This enables attackers to coerce the Keycloak server into making HTTP requests to internal or restricted network resources. As a result, attackers can probe internal services and cloud metadata endpoints, creating an information disclosure and reconnaissance risk.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-1180US | — | — | ||
A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbi… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:6477WEB
- https://access.redhat.com/errata/RHSA-2026:6478WEB
- https://access.redhat.com/security/cve/CVE-2026-1180WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2430781WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/issues/45645WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-1180ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan