{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2025-2559 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-2559 is a medium-severity denial of service vulnerability in Red Hat Build of Keycloak, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2559 and fix it if it is affected.\n\nWhat it is: CVE-2025-2559 is a medium-severity denial of service vulnerability in Red Hat Build of Keycloak, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2559 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.1.4; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.1.4; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-2559/ (Markdown: https://insights.sbomify.com/CVE-2025-2559/index.md)","id":"CVE-2025-2559","markdown":"https://insights.sbomify.com/CVE-2025-2559/index.md","name":"CVE-2025-2559","record":{"aliases":["ECHO-8712-b79a-9acd","GHSA-2935-2wfm-hhpv"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"Attackers can cause denial of service in Keycloak by exhausting JWT token cache memory if long-expiration tokens are used.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Org.keycloak/keycloak-services: jwt token cache exhaustion leading to denial of service (dos) in keycloak","id":"CVE-2025-2559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":6,"next":{"headline":"Ninja Forms \u003c 3.10.1 - Admin+ Stored XSS","id":"CVE-2025-2560"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.1.4"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-2935-2wfm-hhpv"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.1.4"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-2935-2wfm-hhpv"}],"prev":{"headline":"The Wound \u003c= 0.0.1 - Unauthenticated LFI","id":"CVE-2025-2558"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.0"],"published":"2025-03-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["Red Hat"]},"summary":"Attackers can cause denial of service in Keycloak by exhausting JWT token cache memory if long-expiration tokens are used.","url":"https://insights.sbomify.com/CVE-2025-2559/"}