Org.keycloak/keycloak-services: jwt token cache exhaustion leading to denial of service (dos) in keycloak
cve-program · CVE-2025-2559
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-2559 · CVE overview and exploitation status
cve-program · CVE-2025-2559
- https://access.redhat.com/errata/RHSA-2025:4335
- https://access.redhat.com/errata/RHSA-2025:4336
- https://access.redhat.com/security/cve/CVE-2025-2559
- https://bugzilla.redhat.com/show_bug.cgi?id=2353868
- https://github.com/keycloak/keycloak/commit/a10c8119d4452b866b90a9019b2cc159919276ca
- https://github.com/keycloak/keycloak/issues/38576
Related changes
Linked by CVE identifierNo related changes are available here.