{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46389 is a critical authentication bypass vulnerability in defenseunicorns uds-identity-config, published on 5 Jun 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-46389 and fix it if it is affected.\n\nWhat it is: CVE-2026-46389 is a critical authentication bypass vulnerability in defenseunicorns uds-identity-config, published on 5 Jun 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-46389 in the wild and no public exploit code.\n\nAffected product: defenseunicorns uds-identity-config. 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-46389/ (Markdown: https://insights.sbomify.com/CVE-2026-46389/index.md)","id":"CVE-2026-46389","markdown":"https://insights.sbomify.com/CVE-2026-46389/index.md","name":"CVE-2026-46389","record":{"aliases":["GHSA-8mg2-6588-r4hw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity config","requires_auth":"none","summary":"Attackers can bypass client authentication in Keycloak by exploiting a logic error, allowing them to obtain OAuth2 tokens and modify other clients.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uds_identity_config","vendor":"defenseunicorns"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-303","name":"Incorrect Implementation of Authentication Algorithm"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS Core's Identity deployment. In versions 0.11.0 through 0.26.0, a logic error in the `client-kubernetes-secret` Keycloak client authenticator (shipped by `uds-identity-config` and consumed by UDS Core) causes the submitted `client_secret` to be overwritten with the mounted Kubernetes secret before comparison. An attacker who can reach the Keycloak token endpoint and knows a `client_id` using this authenticator can authenticate as that client with any `client_secret` value and obtain OAuth2 tokens scoped to the client's service account. In the case of the `uds-operator` client this token can be used to registry/modify other clients. Version 0.26.1 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`","id":"CVE-2026-46389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"HAX CMS has Unauthenticated Git Access via User-Controlled Key","id":"CVE-2026-46390"},"packages":[],"prev":{"headline":"osquery: Unprivileged users can temporarily read file carve contents","id":"CVE-2026-46388"},"products":["uds-identity-config"],"published":"2026-06-05","related":[],"sources":[{"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-05","vendors":["defenseunicorns"]},"summary":"Attackers can bypass client authentication in Keycloak by exploiting a logic error, allowing them to obtain OAuth2 tokens and modify other clients.","url":"https://insights.sbomify.com/CVE-2026-46389/"}