GPU VulnDB

Database/Control plane, storage & DevOps

UDS Identity Config: Keycloak authenticator accepts any client_secret, granting service-account tokens

CVSS 9.8CVE-2026-46389Control plane, storage & DevOpscurated

Impact

In the client-kubernetes-secret Keycloak authenticator shipped by uds-identity-config, the submitted client_secret is overwritten with the mounted Kubernetes secret before the comparison, so the comparison always succeeds. Anyone who can reach the Keycloak token endpoint and knows a client_id that uses this authenticator gets OAuth2 tokens scoped to that client's service account without knowing any secret. For the uds-operator client that token can register and modify other Keycloak clients, which turns a single token request into control over the cluster's identity configuration - the component every other UDS Core service authenticates against. Knowing the client_id is the only prerequisite, and client ids are not secrets.

Who can reach it

Any network attacker able to reach the Keycloak token endpoint who knows an affected client_id. No valid secret or prior authentication needed.

What to do

Upgrade uds-identity-config to 0.26.1 (affected: 0.11.0 through 0.26.0), rebuild the Keycloak configuration image and roll out the Identity deployment. Restrict the token endpoint to the cluster where possible, and review Keycloak client registrations and changes made while an affected version was running, since the patch does not undo anything an attacker already registered. Pod rollout plus image rebuild - no node maintenance.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.