CVE-2026-46389
OAuth2 token issuance bypass in UDS Identity Config allows token for any client_id.
Is CVE-2026-46389 being exploited?
Not confirmed. CVE-2026-46389 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-46389?
CVE-2026-46389 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46389?
Yes. A fix has been recorded for CVE-2026-46389. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46389 affect?
CVE-2026-46389 affects UDS Identity Config (0.11.0-0.26.0), UDS Core. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46389?
Upgrade to 0.26.1+; rotate secrets; monitor token activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker with token endpoint access can obtain tokens for any client_id; may access/modify other clients.
Patch when possible
- affected>= 0.11.0 and < 0.26.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.