{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7500 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-7500 is a medium-severity missing authorization vulnerability in Redhat Build of Keycloak, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7500 and fix it if it is affected.\n\nWhat it is: CVE-2026-7500 is a medium-severity missing authorization vulnerability in Redhat Build of Keycloak, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-7500 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.6.1; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.1; 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-2026-7500/ (Markdown: https://insights.sbomify.com/CVE-2026-7500/index.md)","id":"CVE-2026-7500","markdown":"https://insights.sbomify.com/CVE-2026-7500/index.md","name":"CVE-2026-7500","record":{"aliases":["ECHO-69cc-b026-014f","GHSA-hm32-hfmw-rhvg","MINI-4wph-75wx-fjpq","MINI-8rg5-9gr6-p585"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can access and modify account data via unsecured API endpoints when the account feature is explicitly disabled in Keycloak.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"}],"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-425","name":"Direct Request"}],"description":"When Keycloak is started with `--features-disabled=account,account-api`, the Account REST API is only partially disabled. Five endpoints under the versioned path `/account/v1alpha1` remain fully functional — including both read and write operations — because they lack the `checkAccountApiEnabled()` gate that correctly blocks four other endpoints in the same REST service class. The user needs to have permissions to use the API.","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 has a Forced Browsing issue","id":"CVE-2026-7500","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak"],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"LinkStackOrg LinkStack UserController.php editPage cross site scripting","id":"CVE-2026-7501"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.6.1"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-hm32-hfmw-rhvg"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.6.1"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-hm32-hfmw-rhvg"}],"prev":{"headline":"Stored XSS in Basamak Informatics' DernekWeb","id":"CVE-2026-7498"},"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.3"],"published":"2026-04-30","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":"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":"Attackers can access and modify account data via unsecured API endpoints when the account feature is explicitly disabled in Keycloak.","url":"https://insights.sbomify.com/CVE-2026-7500/"}