Keycloak TLS Client-Initiated Renegotiation Denial of Service
Keycloak is vulnerable to a Denial of Service (DoS) attack due to the default JDK setting that permits Client-Initiated Renegotiation in TLS 1.2. An unauthenticated remote attacker can repeatedly initiate TLS renegotiation requests to exhaust server CPU resources, making the service unavailable. Immediate mitigation is available by setting the `-Djdk.tls.rejectClientInitiatedRenegotiation=true` Java system property in the Keycloak startup configuration.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-11419US | — | — | ||
A flaw was found in Keycloak. This vulnerability allows an unauthenticated remote attacker to cause a denial of service (DoS) by repeatedly initiating TLS 1.2 client-initiated rene… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2025:18254WEB
- https://access.redhat.com/errata/RHSA-2025:18255WEB
- https://access.redhat.com/errata/RHSA-2025:18889WEB
- https://access.redhat.com/errata/RHSA-2025:18890WEB
- https://access.redhat.com/security/cve/CVE-2025-11419WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2402142WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/discussions/25209WEB
scry
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