CVE-2026-46389: UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`
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 clientsecret to be overwritten with the mounted Kubernetes secret before comparison. An attacker who can reach the Keycloak token endpoint and knows a clientid using this authenticator can authenticate as that client with any clientsecret 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
UDS Identity Configto a version that resolves this vulnerability.Fixed in 0.26.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46389?
CVE-2026-46389 has a critical severity rating of 10.
How do I fix CVE-2026-46389?
To fix CVE-2026-46389, upgrade to UDS Identity Config version 0.26.1 or later.
What impact does CVE-2026-46389 have on my system?
CVE-2026-46389 allows client authentication bypass, potentially allowing unauthorized access.
Which versions of UDS Identity Config are affected by CVE-2026-46389?
CVE-2026-46389 affects UDS Identity Config versions 0.11.0 through 0.26.0.
Is there a workaround for CVE-2026-46389?
No official workaround is available for CVE-2026-46389; upgrading is the recommended solution.