CVE-2026-46389: UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`

Severity: critical (CVSS 9.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-06-05 · updated 2026-10-26
Weakness: CWE-287

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

defenseunicorns uds-identity-config: from 0.11.0 before 0.26.1 — fixed in 0.26.1

How to fix

Upgrade to a fixed version: defenseunicorns uds-identity-config 0.26.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-46389 or the next vulnerability affects your stack