CVE-2025-33116: IBM Watson Studio on Cloud Pak for Data · XSS or 'Cross-site Scripting'
Affects IBM Watson Studio on Cloud Pak for DataSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Watson Studio on Cloud Pak for Data | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Apply any available IBM patches or updates for Watson Studio on Cloud Pak for Data as soon as they are released. 2) Restrict access to Watson Studio to only trusted and necessary users, enforcing strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of compromised accounts. 3) Conduct thorough input validation and output encoding reviews in any custom extensions or integrations with Watson Studio to prevent injection of malicious scripts. 4) Monitor user activity logs for unusual behavior indicative of attempted XSS exploitation or unauthorized script execution. 5) Educate users on the risks of interacting with untrusted content within the platform to reduce the chance of triggering malicious scripts. 6) Employ web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting IBM Watson Studio interfaces. 7) Segment the network environment hosting Watson Studio to limit lateral movement if a session is compromised. 8) Prepare incident response plans specifically addressing potential XSS exploitation scenarios in data science platforms.
Description
IBM Watson Studio 4.0 through 5.2.0 on Cloud Pak for Data is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.