{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93999 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93999 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93999 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 19 Sep 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-93999 and fix it if it is affected.\n\nWhat it is: CVE-2026-93999 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 19 Sep 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-93999 in the wild and no public exploit code.\n\nAffected product: Red Hat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-93999/ (Markdown: https://insights.sbomify.com/CVE-2026-93999/index.md)","id":"CVE-2026-93999","markdown":"https://insights.sbomify.com/CVE-2026-93999/index.md","name":"CVE-2026-93999","record":{"aliases":["GHSA-82wc-7jr6-wxgm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity and access management","requires_auth":"low_privilege","summary":"Attackers with valid refresh tokens can obtain access tokens for disabled clients, bypassing administrative access controls in Keycloak.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A flaw was found in the OIDC protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs during the token refresh process when the server restores requested audiences from stored client IDs. Keycloak fails to verify if the target audience client is still enabled before issuing a new access token. This allows an application with an existing refresh token to continue obtaining valid access tokens for a disabled client, potentially bypassing administrative access controls for resource servers that rely on offline JWT validation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Keycloak-services: keycloak-services: token refresh continues issuing tokens for disabled audience clients","id":"CVE-2026-93999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Red Hat Build of Keycloak","id":"CVE-2026-94000"},"packages":[],"prev":{"headline":"SourceCodester Drug Recommendation System edit_symptom.php sql injection","id":"CVE-2026-93997"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7"],"published":"2026-09-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-22","vendors":["Red Hat"]},"summary":"Attackers with valid refresh tokens can obtain access tokens for disabled clients, bypassing administrative access controls in Keycloak.","url":"https://insights.sbomify.com/CVE-2026-93999/"}