CVE-2026-46389 UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`
Attackers can bypass client authentication in Keycloak by exploiting a logic error, allowing them to obtain OAuth2 tokens and modify other clients.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-46389?
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.
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.
Which versions are affected by CVE-2026-46389?
It affects 1 product.
Products include Defenseunicorns Uds Identity Config.
How do I fix CVE-2026-46389?
No fix has been published for CVE-2026-46389 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-46389 being exploited?
There is no known exploitation of CVE-2026-46389 in the wild and no public exploit code.
Sources
Also known as GHSA-8mg2-6588-r4hw.