CVE 10 CRITICAL

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

10 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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.

AI Analysis

A logic error in the `client-kubernetes-secret` Keycloak client authenticator allows an attacker to authenticate as a client with any `client_secret` value.

Basic Information

ID CVE-2026-46389
Source GitHub_M
Published Jun 5, 2026 at 18:10

Affected Product

Vendor defenseunicorns
Product uds-identity-config
Version >= 0.11.0, < 0.26.1
Affected Versions defenseunicorns uds-identity-config >= 0.11.0, < 0.26.1

CWE Classification

AI Assessment

AI Score 10 / 10
AI Severity Critical
Vendor Defense Unicorns
Product UDS Identity Config
Version 0.11.0-0.26.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.