CVE-2026-46389

UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`

Published Jun 5, 2026 CVSS 3.1 · 10 Critical EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Defenseunicorns uds Identity Config
CPEs cpe:2.3:a:defenseunicorns:uds_identity_config:*:*:*:*:*:*:*:*
Vendors & Products Defenseunicorns uds Identity Config
Type Values Removed Values Added
First Time appeared Defenseunicorns
Defenseunicorns uds-identity-config
Vendors & Products Defenseunicorns
Defenseunicorns uds-identity-config
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title UDS Identity Config has a client authentication bypass in `ClientIdAndKubernetesSecretAuthenticator`
Weaknesses CWE-287
CWE-303
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jun 5, 2026, 7:40 PM
Reserved
May 13, 2026, 7:53 PM
Status
Analyzed
Published
Jun 5, 2026, 7:16 PM
Modified
Oct 26, 2026, 11:10 AM