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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- 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/a10c8119d4452b866b90a9019b2cc1599192
- https://github.com/keycloak/keycloak/issues/38576
FAQ
What is CVE-2025-2559?
CVE-2025-2559 is a vulnerability with a CVSS score of 4.9 (MEDIUM). 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, f...
How severe is CVE-2025-2559?
CVE-2025-2559 has been rated MEDIUM with a CVSS base score of 4.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-2559?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.