Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Keycloak (org.keycloak:keycloak-services, versions up to and including 26.1.4) caches JWT tokens until they expire. An attacker who can get clients to use JWT tokens with very long expiration times can make the cache grow without limit, causing an OutOfMemoryError and denial of service for legitimate users. No fix is listed in the source, and it gives few details on the exact preconditions.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H | CNA (redhat) |
- CISA KEV Not listed.
- EPSS 0.0070, the 53rd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:11 UTC First seen by agentprime
- 31 Oct 2026, 15:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2935-2wfm-hhpv
- OSV: GHSA-2935-2wfm-hhpv
- nvd.nist.gov/vuln/detail/CVE-2025-2559
- 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
- github.com/keycloak/keycloak