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

> Attackers can bypass client authentication in Keycloak by exploiting a logic error, allowing them to obtain OAuth2 tokens and modify other clients.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-8mg2-6588-r4hw

## What is CVE-2026-46389?

CVE-2026-46389 is a critical authentication bypass vulnerability in defenseunicorns uds-identity-config, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-46389?

It affects 1 product.


Products: Defenseunicorns Uds Identity Config.

## How do I fix CVE-2026-46389?

No fix has been published for CVE-2026-46389 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46389 being exploited?

There is no known exploitation of CVE-2026-46389 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46389 and fix it if it is affected.

What it is: CVE-2026-46389 is a critical authentication bypass vulnerability in defenseunicorns uds-identity-config, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46389 in the wild and no public exploit code.

Affected product: defenseunicorns uds-identity-config. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46389/ (Markdown: https://insights.sbomify.com/CVE-2026-46389/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46389
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46389
- OSV: https://osv.dev/vulnerability/CVE-2026-46389

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46389/
Summaries are generated and may contain mistakes; the official description above is the record.