Skip to main content

IBM watsonx Orchestrate CVE-2025-1837

| EUVDEUVD-2025-211278 MEDIUM
Trusting HTTP Permission Methods on the Server Side (CWE-650)
2026-11-08 ibm GHSA-h693-cjhw-whmq
5.4
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to watsonx Orchestrate interface
  2. Exploit
    Craft request abusing trusted permission method
  3. Execution
    Bypass server-side authorization check
  4. Impact
    Perform unauthorized action on data

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

Exploitation requires an authenticated user account on watsonx Orchestrate Cartridge for Cloud Pak for Data (versions 4.8.4 through 4.8.5 and 5.0.0 through 5.4.2); the application improperly trusts server-side permission methods (CWE-650), letting a logged-in user perform actions beyond their authorization. The CVSS vector's UI:R indicates some user interaction may be involved, and the scope is unchanged (S:U), limiting impact to the vulnerable component. Limiting factors: a valid account is needed per the description (despite the vector's PR:N), impact is partial (C:L/I:L, no availability), and fixed versions are available from the vendor. Note the description-versus-vector disagreement on whether authentication is required - confirm with IBM before scoping as unauthenticated.

Impact

This is a moderate-severity authorization flaw (CVSS 5.4) that is best treated as a routine, scheduled-patch item rather than an urgent priority. The input provides no EPSS score, no CISA KEV listing, and no PoC/exploit reference, and the vendor-assigned severity is only medium with partial confidentiality and integrity impact and no availability impact. A notable conflict exists in the source data: the CVSS vector encodes PR:N (no privileges), yet the description explicitly states 'an authenticated user' must perform the action - these disagree, and the description's requirement for authentication should be weighted as the more specific signal, meaning real exploitation requires a valid account rather than anonymous access (verify privilege requirement with IBM advisory 7293785). The underlying weakness (CWE-650, improper server-side trust of permission methods) indicates a privilege/authorization boundary that can be subverted by a logged-in user, not a pre-authentication compromise. The vuln.today decision label is 'this_month', consistent with medium severity and the absence of active-exploitation signals. Overall this is a genuine but low-urgency authorization issue - not a high-CVSS-but-illusory risk, but also not an emergency.

Exploit ScenarioDerived

An authenticated user of watsonx Orchestrate Cartridge for Cloud Pak for Data crafts a request that relies on the server improperly trusting the HTTP method or a server-side permission check, allowing them to invoke an action they are not authorized for. Because the vector is network-based with low complexity, the request can be issued remotely over the application's normal interface. No public exploit code or PoC reference is present in the provided data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 08, 2026

An authorization weakness in the IBM watsonx Orchestrate Cartridge for Cloud Pak for Data (versions 4.8.4 through 4.8.5 and 5.0.0 through 5.4.2) lets a user who already holds an account on the cartridge perform actions that should have been blocked by their assigned permissions, because the application improperly trusts server-side permission methods (CWE-650). Impact is bounded: scope is unchanged and only partial confidentiality and integrity effects are assessed (CVSS 5.4), with no availability impact. There is no public exploit identified at time of analysis and the issue does not appear on CISA KEV; IBM has published a fix advisory, and the vulnerability is best scheduled for patching this month rather than treated as an emergency. Note a data discrepancy worth resolving with the vendor: the supplied vector is PR:N (unauthenticated) while the description and independent assessment require a valid account (PR:L), and the vector also carries UI:R whereas the independent assessment uses UI:N.

RemediationAI

IBM has released a fix for this issue, published through the vendor advisory at https://www.ibm.com/support/pages/node/7293785 (patch available from vendor); the supplied data does not enumerate the exact fixed build numbers per branch, so the precise target release for 4.8.x and for 5.x should be taken from that advisory and the cartridge upgraded accordingly during the current monthly patch cycle. No workaround or configuration-level mitigation is stated in the available sources, and updating to the fixed cartridge build is the complete fix per the vendor guidance; if a deployment cannot be updated immediately, the only lever supported by the evidence is reducing exposure of the cartridge to accounts that do not need it, since the flaw is exercised by an already-authenticated user acting outside their granted permissions. Before finalizing scope, confirm with IBM whether a valid account is genuinely required, given the disagreement between the published vector (PR:N) and the description and independent assessment (account required).

Affected VersionsENISA

watsonx Orchestrate Cartridge for Cloud Pak for Data 5.0.0 ≤5.4.2
watsonx Orchestrate Cartridge for Cloud Pak for Data 4.8.4 ≤4.8.5

Affected Packages

euvd watsonx_orchestrate_cartridge_for_cloud_pak_for_data no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the watsonx Orchestrate Cartridge deployed on IBM Cloud Pak for Data, and the CPE entry is a fully wildcarded product match (cpe:2.3:a:ibm:watsonx_orchestrate_cartridge_for_cloud_pak_for_data:*:*:*:*:*:*:*:*), so affectedness must be scoped by the version ranges named by IBM rather than by a granular CPE version. The root-cause class is CWE-650, Trusting HTTP Permission Methods on the Server Side: authorization decisions are made on a value the client can influence - the permission method the server trusts - instead of being re-derived from the caller's actual entitlements. In practical terms the check that should gate a privileged operation is satisfied by trusting a server-side permission method that the application does not adequately bind to the authenticated identity, so a lower-privileged account can reach functionality reserved for another role. The available sources do not describe the specific request sequence, endpoint, or code path that triggers the bypass, so the trigger is not described in the available sources beyond the CWE class. Exploitation prerequisites are themselves contested in the supplied data: the vendor text and the independent assessment assume a valid authenticated account, while the published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) describes a network-reachable issue with no privileges required and required user interaction. Scope is unchanged, which keeps the blast radius inside the cartridge rather than crossing a trust boundary into the underlying Cloud Pak for Data platform.

Know when Watsonx Orchestrate Cartridge For Cloud Pak For Data gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY MEDIUM
NVD 5.4 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Description requires an authenticated user, so PR:L rather than the input's PR:N; network low-complexity access yields partial confidentiality and integrity impact, no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionNVD

IBM watsonx Orchestrate Cartridge for Cloud Pak for Data 4.8.4 through 4.8.5, and 5.0.0 through 5.4.2 could allow an authenticated user to perform unauthorized actions due to improper trust of server-side permission methods.

Threat Intelligence Overview

Prevalence
Low
IBM enterprise AI cartridge for Cloud Pak for Data, specialized deployment footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy