dbcve.org
Uds Identity ConfigApplication · Defenseunicorns

CVE-2026-46389

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 0.26.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A logic error in the client-kubernetes-secret Keycloak authenticator causes the submitted client_secret to be overwritten with a mounted Kubernetes secret before comparison. This allows authentication bypass using any client_secret value for clients using this authenticator, enabling attackers to obtain OAuth2 tokens and potentially modify other clients.

MitigationUpgrade UDS Identity Config to version 0.26.1 or later. Additionally, review Keycloak client configurations to identify which clients use the affected authenticator and consider rotating credentials as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Uds Identity ConfigApplication
Affected:>= 0.11.0, < 0.26.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check uds-identity-config version
    Inspect your deployment manifests, Helm values, or container image tags for the installed version of Defenseunicorns Uds Identity Config. Look for version tags like '0.11.0', '0.20.0', '0.26.0', etc.
    Affected if Version is 0.11.0 through 0.26.0 inclusive, or any version below 0.26.1
  2. Identify if client-kubernetes-secret authenticator is in use
    Review your Keycloak client configurations to determine if any clients are configured to use the 'client-kubernetes-secret' authenticator. Check the client authenticator settings in the Keycloak admin console or exported realm configurations.
    Affected if A Keycloak client is configured to use the client-kubernetes-secret authenticator
  3. Verify the vulnerable code path exists
    If possible, examine the uds-identity-config deployment for the presence of files or configurations related to the kubernetes-secret client authenticator. This authenticator should mount a Kubernetes secret and use it for comparison.
    Affected if The deployment contains the client-kubernetes-secret authenticator implementation and it is actively processing authentication requests

You are affected if uds-identity-config versions 0.11.0 through 0.26.0 are deployed AND the client-kubernetes-secret Keycloak client authenticator is actively configured for any client.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.26.1 or later
Fixed in 0.26.1
Interim mitigation

Upgrade UDS Identity Config to version 0.26.1 or later. Additionally, review Keycloak client configurations to identify which clients use the affected authenticator and consider rotating credentials as a precautionary measure.

Recommended fix High confidence

0.26.1

  1. Upgrade UDS Identity Config from any version >= 0.11.0 and < 0.26.1 to version 0.26.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uds Identity Config Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46389 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data