Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-36139: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in IBM watsonx.data

0
Medium
VulnerabilityCVE-2025-36139cvecve-2025-36139cwe-79
Published: Thu Sep 18 2025 (09/18/2025, 15:13:10 UTC)
Source: CVE Database V5
Vendor/Project: IBM
Product: watsonx.data

Description

IBM Lakehouse (watsonx.data 2.2) is vulnerable to stored cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

AI-Powered Analysis

AILast updated: 09/26/2025, 01:01:54 UTC

Technical Analysis

CVE-2025-36139 is a stored cross-site scripting (XSS) vulnerability identified in IBM watsonx.data version 2.2, part of the IBM Lakehouse platform. The vulnerability arises from improper neutralization of input during web page generation (CWE-79), allowing a privileged user to embed arbitrary JavaScript code into the web user interface. Because the vulnerability is stored XSS, the malicious script persists on the server and executes whenever a victim accesses the affected page. The attack vector requires network access and privileges (PR:H), but no user interaction is needed once the malicious script is stored. The vulnerability impacts confidentiality and integrity by potentially enabling credential disclosure within a trusted session and altering intended functionality of the web application. The CVSS 3.1 base score is 5.5 (medium severity), reflecting that the attack can be launched remotely with low complexity but requires privileged user access. The scope is changed (S:C), meaning the vulnerability affects resources beyond the vulnerable component. No known exploits are currently in the wild, and no patches have been linked yet. The vulnerability is significant because IBM watsonx.data is used for data lakehouse management, often containing sensitive enterprise data, and the web UI is a critical interface for administrators and users. Exploitation could lead to session hijacking, credential theft, or unauthorized actions within the trusted environment.

Potential Impact

For European organizations using IBM watsonx.data 2.2, this vulnerability poses a risk to the confidentiality and integrity of sensitive data managed within the platform. Since the vulnerability allows a privileged user to inject malicious scripts, insider threats or compromised privileged accounts could lead to credential theft or session hijacking, potentially escalating further attacks or data exfiltration. The alteration of web UI functionality could disrupt normal operations or mislead users into performing unintended actions. Given the critical role of data lakehouse platforms in analytics and data governance, exploitation could impact compliance with GDPR and other data protection regulations by exposing personal or sensitive data. Additionally, the persistence of the malicious script increases the risk of prolonged exposure until the vulnerability is remediated. The medium severity score suggests moderate urgency, but the requirement for privileged access limits the attack surface to trusted users or attackers who have already gained elevated access.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict and monitor privileged user access rigorously, employing the principle of least privilege and strong authentication methods such as multi-factor authentication (MFA). 2) Conduct thorough input validation and sanitization on all user inputs, especially those that can be rendered in the web UI, to prevent injection of malicious scripts. 3) Deploy web application firewalls (WAFs) with custom rules to detect and block suspicious script payloads targeting the IBM watsonx.data interface. 4) Monitor logs and user activities for unusual behavior indicative of attempted or successful exploitation, focusing on privileged accounts. 5) Apply security patches promptly once IBM releases them; meanwhile, consider temporary workarounds such as disabling or limiting access to vulnerable UI components if feasible. 6) Educate privileged users about the risks of XSS and safe usage practices. 7) Regularly review and update security policies related to web application security and privileged access management. These targeted actions go beyond generic advice by focusing on the specific threat vector and the privileged nature of the vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
ibm
Date Reserved
2025-04-15T21:16:19.008Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68cc237367c782851fe31854

Added to database: 9/18/2025, 3:21:23 PM

Last enriched: 9/26/2025, 1:01:54 AM

Last updated: 12/18/2025, 7:48:25 PM

Views: 55

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats