REDHAT-BUG-2353868
First published: Thu Mar 20 2025(Updated: )
A trusted client with long-lived JWT tokens can cause memory exhaustion in Keycloak due to unbounded token caching.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Keycloak |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of REDHAT-BUG-2353868?
The severity of REDHAT-BUG-2353868 is critical due to its potential to cause memory exhaustion.
How do I fix REDHAT-BUG-2353868?
To fix REDHAT-BUG-2353868, configure Keycloak to limit the lifetime of JWT tokens or manage token caching strategies.
What software is affected by REDHAT-BUG-2353868?
REDHAT-BUG-2353868 affects Red Hat Keycloak, particularly in regards to its handling of long-lived JWT tokens.
What is the cause of the issue in REDHAT-BUG-2353868?
The cause of the issue in REDHAT-BUG-2353868 is unbounded token caching leading to memory exhaustion.
Can I prevent REDHAT-BUG-2353868 from occurring?
Yes, you can prevent REDHAT-BUG-2353868 by implementing proper token expiry settings and limiting the number of cached tokens.
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2025-2559
- agent/last-modified-date
- agent/references
- agent/source
- agent/severity
- agent/type
- agent/description
- agent/first-publish-date
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/red hat
- canonical/keycloak