{"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-9793 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-9793 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9793 and fix it if it is affected.\n\nWhat it is: CVE-2026-9793 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9793 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.4; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.4; 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-9793/ (Markdown: https://insights.sbomify.com/CVE-2026-9793/index.md)","id":"CVE-2026-9793","markdown":"https://insights.sbomify.com/CVE-2026-9793/index.md","name":"CVE-2026-9793","record":{"aliases":["ECHO-70df-01df-0cb2","GHSA-p3v8-fm5p-v84h","MINI-gv76-rvvc-9gpw","MINI-j3jm-973v-9q3c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Remote attackers can bypass signature policies in Keycloak's JWE processing to submit unauthorized claims, compromising OIDC data integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"A flaw was found in Keycloak. When a JSON Web Encryption (JWE) encrypted request object is submitted, Keycloak may incorrectly process unsigned claims if the decrypted content is raw JSON, bypassing the configured signature policy. This allows a remote attacker to submit unauthorized claims, leading to a compromise of data integrity within the OpenID Connect (OIDC) authorization flow. While a redirect URI allowlist acts as a compensating control, this vulnerability violates OIDC Core and Financial-grade API (FAPI) signing requirements.","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: keycloak: security policy bypass in jwe-encrypted request object processing","id":"CVE-2026-9793","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak"],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"Keycloak: keycloak: information disclosure via saml ecp endpoint","id":"CVE-2026-9794"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.6.4"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-p3v8-fm5p-v84h"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.6.4"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-p3v8-fm5p-v84h"}],"prev":{"headline":"Keycloak: keycloak: security restriction bypass allows unauthorized ropc token acquisition","id":"CVE-2026-9792"},"products":["Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.14","Red Hat build of Keycloak 26.6","Red Hat build of Keycloak 26.6.5"],"published":"2026-05-28","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-08-20","vendors":["Red Hat"]},"summary":"Remote attackers can bypass signature policies in Keycloak's JWE processing to submit unauthorized claims, compromising OIDC data integrity.","url":"https://insights.sbomify.com/CVE-2026-9793/"}