A trusted client with long-lived JWT tokens can cause memory exhaustion in Keycloak due to unbounded token caching.
This issue has been addressed in the following products: Red Hat build of Keycloak 22 Via RHSA-2025:4336 https://access.redhat.com/errata/RHSA-2025:4336
This issue has been addressed in the following products: Red Hat build of Keycloak 26.0 Via RHSA-2025:4335 https://access.redhat.com/errata/RHSA-2025:4335