A flaw was found in Keycloak. When the configuration uses JWT tokens for authentication, the tokens are cached until expiration. If a client uses JWT tokens with an excessively long expiration time, for example, 24 or 48 hours, the cache can grow indefinitely, leading to an OutOfMemoryError. This issue could result in a denial of service condition, preventing legitimate users from accessing the system.
Metrics
Affected Vendors & Products
References
History
Wed, 26 Mar 2025 02:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
threat_severity
|
Tue, 25 Mar 2025 08:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | A flaw was found in Keycloak. When the configuration uses JWT tokens for authentication, the tokens are cached until expiration. If a client uses JWT tokens with an excessively long expiration time, for example, 24 or 48 hours, the cache can grow indefinitely, leading to an OutOfMemoryError. This issue could result in a denial of service condition, preventing legitimate users from accessing the system. | |
Title | Org.keycloak/keycloak-services: jwt token cache exhaustion leading to denial of service (dos) in keycloak | |
First Time appeared |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
Weaknesses | CWE-770 | |
CPEs | cpe:/a:redhat:build_keycloak: cpe:/a:redhat:red_hat_single_sign_on:7 |
|
Vendors & Products |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: redhat
Published: 2025-03-25T08:20:57.666Z
Updated: 2025-03-25T08:20:57.666Z
Reserved: 2025-03-20T12:22:59.504Z
Link: CVE-2025-2559

No data.

Status : Received
Published: 2025-03-25T09:15:17.047
Modified: 2025-03-25T09:15:17.047
Link: CVE-2025-2559
