watsonx Orchestrate Cartridge EUVD-2026-119709

Requires a valid authenticated low-privileged user account on an affected deployment (CVSS PR:L) - exploitation is not possible pre-authentication. The specific prerequisite is that administrative operations are exposed through backend APIs that perform authorization only at the UI layer; an attacker invokes those backend API endpoints directly to bypass the UI-level restrictions. No user interaction is required (UI:N) and the attack is network-reachable (AV:N). Limiting factors: the affected versions are IBM watsonx Orchestrate Cartridge for Cloud Pak for Data 4.8.4 through 4.8.5 and 5.0.0 through 5.4.2 only; the attacker must already possess credentials, which bounds this to insider or post-compromise abuse rather than mass unauthenticated exploitation.

This is a broken access control / missing server-side RBAC issue (CWE-284): the backend fails to enforce role-based checks, so UI-level restrictions can be bypassed by directly invoking backend APIs. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, base 4.3) indicates a network-reachable, low-complexity flaw that requires an already-authenticated low-privileged account (PR:L) - it is a privilege-escalation / authorization bypass, not an unauthenticated authentication bypass. The modeled impact is limited to integrity (I:L) with no confidentiality or availability impact, consistent with a MEDIUM severity. No EPSS score, CISA KEV listing, SSVC decision, or PoC/exploit reference is present in the input, so there is no signal of active or probable exploitation; the vuln.today decision label is 'this_month' (a routine-priority, not act_now/emergency, cadence). Real-world priority is moderate and primarily insider/post-authentication: the main gating factor is that an attacker must first hold valid low-privileged credentials on the affected deployment, which bounds mass exploitation. Note the modeled integrity impact of I:L appears conservative given the description says low-privileged users can 'execute administrative functions,' which could in practice enable higher integrity (and possibly confidentiality) impact depending on which admin APIs are exposed - verify the concrete admin capabilities with IBM advisory node 7293785.

An attacker who already holds a valid low-privileged account on an affected Cloud Pak for Data deployment bypasses the UI, which hides administrative controls, and sends crafted requests directly to the backend administrative API endpoints. Because the backend does not re-check the caller's role, the low-privileged user successfully performs administrative operations they should not be authorized to perform. No public exploit or PoC reference is provided in the input, and no user interaction is required.