{"answers":{"affected":"1 open source package ship an affected version, including keycloak. It affects 4 products.","exploited":"There is no known exploitation of CVE-2026-16102 in the wild and no public exploit code.","fix":"Upgrade keycloak to a fixed version for your release line: 26.4.14 or 26.6.5.","what":"CVE-2026-16102 is a high-severity vulnerability in Redhat Build of Keycloak, published on 5 Aug 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-16102 and fix it if it is affected.\n\nWhat it is: CVE-2026-16102 is a high-severity vulnerability in Redhat Build of Keycloak, published on 5 Aug 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-16102 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keycloak (Bitnami): affected from 26.4.0; fixed in 26.4.14, 26.6.5\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-16102/ (Markdown: https://insights.sbomify.com/CVE-2026-16102/index.md)","id":"CVE-2026-16102","markdown":"https://insights.sbomify.com/CVE-2026-16102/index.md","name":"CVE-2026-16102","record":{"aliases":["BIT-keycloak-2026-16102","GHSA-6x4h-v8cp-whwh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity management","requires_auth":"low_privilege","summary":"Attackers with standard accounts can forge administrative roles via flawed Dynamic Client Registration policies, gaining full realm control.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"},{"product":"data_grid","vendor":"redhat"},{"product":"jboss_enterprise_application_platform_expansion_pack","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-551","name":"Incorrect Behavior Order: Authorization Before Parsing and Canonicalization"}],"description":"A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive internal claim locations. An attacker with a standard user account and a limited Initial Access Token can exploit this to forge administrative roles in their access token. This allows the attacker to take over other clients, steal confidential secrets, and potentially gain full administrative control over the realm.","ecosystems":["Bitnami"],"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: keycloak-services: default dcr policy allows role forgery via user property mappers","id":"CVE-2026-16102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak","redhat:single_sign-on"],"type":"privilege_escalation","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"Keycloak-services: keycloak-services: incomplete fix for ciba brute-force lockout bypass at token redemption","id":"CVE-2026-16103"},"packages":[{"ecosystem":"Bitnami","fixed":["26.4.14","26.6.5"],"introduced":["26.4.0","26.6.0"],"last_affected":[],"package":"keycloak","purl":"pkg:bitnami/keycloak","source":"BIT-keycloak-2026-16102"}],"prev":{"headline":"forced re-pairing with already bonded device","id":"CVE-2026-16101"},"products":["Red Hat Data Grid 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Single Sign-On 7","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-08-05","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":"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":"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":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["Red Hat"]},"summary":"Attackers with standard accounts can forge administrative roles via flawed Dynamic Client Registration policies, gaining full realm control.","url":"https://insights.sbomify.com/CVE-2026-16102/"}