{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2025-12110 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to 26.2.3 or later.","what":"CVE-2025-12110 is a medium-severity vulnerability in Red Hat build of Keycloak 26.2, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12110 and fix it if it is affected.\n\nWhat it is: CVE-2025-12110 is a medium-severity vulnerability in Red Hat build of Keycloak 26.2, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12110 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.3\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.3\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-12110/ (Markdown: https://insights.sbomify.com/CVE-2025-12110/index.md)","id":"CVE-2025-12110","markdown":"https://insights.sbomify.com/CVE-2025-12110/index.md","name":"CVE-2025-12110","record":{"aliases":["ECHO-6fb2-4b82-1991","GHSA-895x-rfqp-jh5c","MINI-9c7w-jxp3-vj6g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can maintain access via offline sessions even after administrators remove the offline_access scope from a client configuration.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"A flaw was found in Keycloak. An offline session continues to be valid when the offline_access scope is removed from the client. The refresh token is accepted and you can continue to request new tokens for the session. As it can lead to a situation where an administrator removes the scope, and assumes that offline sessions are no longer available, but they are.","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":"Keycloak does not invalidate offline sessions when the offline_access scope is removed","id":"CVE-2025-12110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":7,"next":{"headline":"Insert Headers and Footers Code – HT Script \u003c= 1.1.6 - Authenticated (Author+) Stored Cross-Site Scripting","id":"CVE-2025-12112"},"packages":[{"ecosystem":"Maven","fixed":["26.2.3"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-895x-rfqp-jh5c"},{"ecosystem":"Maven","fixed":["26.2.3"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-895x-rfqp-jh5c"}],"prev":{"headline":"Cross-site scripting in Header Footer Script Adder – Insert Code in Header, Body \u0026 Footer","id":"CVE-2025-12109"},"products":["Red Hat build of Keycloak 26.2","Red Hat build of Keycloak 26.2.11","Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.4","keycloak"],"published":"2025-10-23","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-01-20","vendors":["Keycloak","Red Hat"]},"summary":"Attackers can maintain access via offline sessions even after administrators remove the offline_access scope from a client configuration.","url":"https://insights.sbomify.com/CVE-2025-12110/"}