Vulnerability · Published Jun 5, 2026 · Assigned by GitHub_M
CVE-2026-46389UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`
Critical 10.0
In plain English
A critical-severity improper authentication in uds-identity-config from defenseunicorns. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 28% of all known vulnerabilities).
Official 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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| defenseunicorns | uds-identity-config | >= 0.11.0, < 0.26.1 |
Weakness: CWE-287, CWE-303 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H