CVE-2026-46389: defenseunicorns uds-identity-config · Improper Authentication
Affects defenseunicorns uds-identity-configSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.26.1 as a priority.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.26.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade uds-identity-config and defenseunicorns/uds-identity-config to 0.26.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| defenseunicornsuds-identity-config | Affected
| Fixed in
|
GitHubdefenseunicorns/uds-identity-configpkg:github/defenseunicorns/uds-identity-configOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Version 0.26.1 of uds-identity-config contains a patch that fixes this authentication bypass vulnerability. Users should upgrade to version 0.26.1 or later to remediate the issue. No vendor advisory or official patch link was provided, so verify the upgrade availability and instructions from the defenseunicorns project repository or official channels.
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.