{"answers":{"affected":"4 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2025-1391 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.0.10 or 26.1.3.","what":"CVE-2025-1391 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 17 Feb 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-1391 and fix it if it is affected.\n\nWhat it is: CVE-2025-1391 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 17 Feb 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-1391 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.0.10\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.0.10\n- org.keycloak:keycloak-services (Maven): affected from 26.1.0; fixed in 26.1.3\n- org.keycloak:keycloak-services (Maven): affected from 26.1.0; fixed in 26.1.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-1391/ (Markdown: https://insights.sbomify.com/CVE-2025-1391/index.md)","id":"CVE-2025-1391","markdown":"https://insights.sbomify.com/CVE-2025-1391/index.md","name":"CVE-2025-1391","record":{"aliases":["ECHO-b87a-6495-4598","GHSA-gvgg-2r3r-53x7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can gain unauthorized organization privileges by matching domain patterns, leading to incorrect access control decisions in applications relying on Keycloak tokens.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-284","name":"Improper Access Control"}],"description":"A flaw was found in the Keycloak organization feature, which allows the incorrect assignment of an organization to a user if their username or email matches the organization’s domain pattern. This issue occurs at the mapper level, leading to misrepresentation in tokens. If an application relies on these claims for authorization, it may incorrectly assume a user belongs to an organization they are not a member of, potentially granting unauthorized access or privileges.","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-services: improper authorization in keycloak organization mapper allows unauthorized organization claims","id":"CVE-2025-1391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":4,"n_references":6,"next":{"headline":"D-Link DIR-816 index.html cross site scripting","id":"CVE-2025-1392"},"packages":[{"ecosystem":"Maven","fixed":["26.0.10"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-gvgg-2r3r-53x7"},{"ecosystem":"Maven","fixed":["26.0.10"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-gvgg-2r3r-53x7"},{"ecosystem":"Maven","fixed":["26.1.3"],"introduced":["26.1.0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-gvgg-2r3r-53x7"},{"ecosystem":"Maven","fixed":["26.1.3"],"introduced":["26.1.0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-gvgg-2r3r-53x7"}],"prev":{"headline":"pam_cap: Fix potential configuration parsing error","id":"CVE-2025-1390"},"products":["Red Hat Build of Keycloak","Red Hat build of Keycloak 26.0"],"published":"2025-02-17","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 gain unauthorized organization privileges by matching domain patterns, leading to incorrect access control decisions in applications relying on Keycloak tokens.","url":"https://insights.sbomify.com/CVE-2025-1391/"}