{"answers":{"affected":"3 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9083 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to 26.6.4 or later.","what":"CVE-2026-9083 is a medium-severity path traversal vulnerability in Redhat Build of Keycloak, published on 25 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9083 and fix it if it is affected.\n\nWhat it is: CVE-2026-9083 is a medium-severity path traversal vulnerability in Redhat Build of Keycloak, published on 25 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9083 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.6.4\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.6.4\n- keycloak (Bitnami): affected from 26.4.0; fixed in 26.4.13, 26.6.4\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-2026-9083/ (Markdown: https://insights.sbomify.com/CVE-2026-9083/index.md)","id":"CVE-2026-9083","markdown":"https://insights.sbomify.com/CVE-2026-9083/index.md","name":"CVE-2026-9083","record":{"aliases":["BIT-keycloak-2026-9083","GHSA-9jrw-8xf7-xqhq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"A realm administrator can probe arbitrary filesystem paths via keystore parameters, disclosing file existence and readability to identify targets for further attacks.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A flaw was found in Keycloak. A realm administrator with the \"manage-realm\" role can exploit this vulnerability by submitting an arbitrary filesystem path as a keystore parameter when creating a key provider component. This allows the administrator to probe arbitrary filesystem paths, determining which files exist and are readable by the Keycloak process. This information disclosure could be used to identify high-value targets for follow-on attacks.","ecosystems":["Bitnami","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: keycloak: information disclosure through arbitrary filesystem path probing","id":"CVE-2026-9083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak"],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":6,"next":{"headline":"MISP OIDC authentication bypass via automatic email-based account linking under insecure IdP configurations","id":"CVE-2026-9084"},"packages":[{"ecosystem":"Bitnami","fixed":["26.4.13","26.6.4"],"introduced":["26.4.0","26.6.0"],"last_affected":[],"package":"keycloak","purl":"pkg:bitnami/keycloak","source":"BIT-keycloak-2026-9083"},{"ecosystem":"Maven","fixed":["26.6.4"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-9jrw-8xf7-xqhq"},{"ecosystem":"Maven","fixed":["26.6.4"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-9jrw-8xf7-xqhq"}],"prev":{"headline":"Drupal Core SQL Injection","id":"CVE-2026-9082"},"products":["Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.13","Red Hat build of Keycloak 26.6","Red Hat build of Keycloak 26.6.4"],"published":"2026-06-25","related":[{"cvss_score":8.8,"headline":"Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation","id":"CVE-2026-15572","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.8,"headline":"Keycloak SAML Broken has Authentication Bypass by Primary Weakness","id":"CVE-2026-3047","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher","id":"CVE-2026-15573","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers","id":"CVE-2026-16102","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users","id":"CVE-2026-1609","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":8.1,"headline":"Org.keycloak:keycloak-services: keycloak: authentication bypass via jwt algorithm confusion","id":"CVE-2026-11800","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.1,"headline":"Keycloak-policy-enforcer: keycloak policy enforcer: authorization bypass via incorrect uri comparison","id":"CVE-2026-9800","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"US public information, NVD API terms","name":"NVD"},{"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-06-26","vendors":["Red Hat"]},"summary":"A realm administrator can probe arbitrary filesystem paths via keystore parameters, disclosing file existence and readability to identify targets for further attacks.","url":"https://insights.sbomify.com/CVE-2026-9083/"}