CVE-2025-11419

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2025-11419 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (26.0.16, 26.2.10, 26.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-11419? CVE-2025-11419 is a high-severity uncontrolled resource consumption vulnerability in org.keycloak:keycloak-quarkus-dist (maven), affecting versions < 26.0.16. It is fixed in 26.0.16, 26.2.10, 26.4.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2025-11419? CVE-2025-11419 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.keycloak:keycloak-quarkus-dist are affected by CVE-2025-11419? org.keycloak:keycloak-quarkus-dist (maven) versions < 26.0.16 is affected.
4. Is there a fix for CVE-2025-11419? Yes. CVE-2025-11419 is fixed in 26.0.16, 26.2.10, 26.4.1. Upgrade to this version or later.
5. Is CVE-2025-11419 exploitable, and should I be worried? Whether CVE-2025-11419 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-11419 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-11419?
   • Upgrade org.keycloak:keycloak-quarkus-dist to 26.0.16 or later
   • Upgrade org.keycloak:keycloak-quarkus-dist to 26.2.10 or later
   • Upgrade org.keycloak:keycloak-quarkus-dist to 26.4.1 or later