Skip to main content
CVE-2026-2700VulnerabilityPublished

IBM watsonx Orchestrate Cartridge for Cloud Pak for Data 4.8.4 through 4.8.5, and 5.0.0 through 5.4.2 allows

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-2700· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 9 Nov 2026, 00:32 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ibm)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
IBMwatsonx Orchestrate Cartridge for Cloud Pak for DataAffected
  • >=4.8.4 <=4.8.5
  • >=5.0.0 <=5.4.2
Fixed in–
Mavencom.ibm/watsonx-orchestrate-cartridge-for-cloud-pak-for-datapkg:maven/com.ibm/watsonx-orchestrate-cartridge-for-cloud-pak-for-dataOther threatsAffected
  • >=4.8.4 <=4.8.5
  • >=5.0.0 <=5.4.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the affected versions and monitor for updates from IBM. Avoid granting unnecessary privileges to users to reduce risk.

Description

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 contains a vulnerability that allows low-privileged users to execute administrative functions by directly invoking backend APIs. This bypasses UI-level access controls because the backend does not enforce role-based access control properly.

References

Community reviews

Loading reviews…