{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2025-14083 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-14083 is a low-severity vulnerability in Red Hat build of Keycloak 26.4, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14083 and fix it if it is affected.\n\nWhat it is: CVE-2025-14083 is a low-severity vulnerability in Red Hat build of Keycloak 26.4, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-14083 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.2.5; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.2.5; 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-14083/ (Markdown: https://insights.sbomify.com/CVE-2025-14083/index.md)","id":"CVE-2025-14083","markdown":"https://insights.sbomify.com/CVE-2025-14083/index.md","name":"CVE-2025-14083","record":{"aliases":["GHSA-594w-2fwp-jwrc","MINI-h2xr-jpqj-f92c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"Improper access control in Keycloak Admin REST API exposes backend schema and rules, enabling information disclosure and potential privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"A flaw was found in the Keycloak Admin REST API. This vulnerability allows the exposure of backend schema and rules, potentially leading to targeted attacks or privilege escalation via improper access control.","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-server: keycloak: improper access control in admin rest api leads to information disclosure","id":"CVE-2025-14083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":4,"next":{"headline":"youlaitech youlai-mall orders improper control of dynamically-identified variables","id":"CVE-2025-14085"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.2.5"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-594w-2fwp-jwrc"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.2.5"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-594w-2fwp-jwrc"}],"prev":{"headline":"Keycloak Admin REST (Representational State Transfer) API does not properly enforce permissions","id":"CVE-2025-14082"},"products":["Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.11"],"published":"2026-01-21","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-04-02","vendors":["Red Hat"]},"summary":"Improper access control in Keycloak Admin REST API exposes backend schema and rules, enabling information disclosure and potential privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-14083/"}