CVE-2025-2559
A flaw was found in Keycloak. When the configuration uses JWT …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/errata/RHSA-2025:4335
- access.redhat.com/errata/RHSA-2025:4336
- access.redhat.com/security/cve/CVE-2025-2559
- bugzilla.redhat.com/show_bug.cgi?id=2353868
- nvd.nist.gov/vuln/detail/CVE-2025-2559
- github.com/advisories/GHSA-2935-2wfm-hhpv
- github.com/keycloak/keycloak/commit/a10c8119d4452b866b90a9019b2cc159919276ca
- github.com/keycloak/keycloak/issues/38576
- nvd.nist.gov/vuln/detail/CVE-2025-2559
- cve.org/CVERecord?id=CVE-2025-2559
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.