CVE-2025-2559
Keycloak JWT Token Cache Denial of Service Vulnerability
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.
INFO
Published Date :
March 25, 2025, 9:15 a.m.
Last Modified :
April 30, 2025, 3:15 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2025-2559
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Configure JWT tokens with shorter expiration times.
- Monitor and manage the JWT token cache size.
- Update Keycloak to a patched version if available.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-2559.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-2559 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-2559
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-2559 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-2559 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
Apr. 30, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:4336 -
CVE Modified by [email protected]
Apr. 29, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:4335 -
New CVE Received by [email protected]
Mar. 25, 2025
Action Type Old Value New Value 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. Added CVSS V3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-770 Added Reference https://access.redhat.com/security/cve/CVE-2025-2559 Added Reference https://bugzilla.redhat.com/show_bug.cgi?id=2353868