CVE-2025-36146: IBM watsonx.data · Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affects IBM watsonx.dataSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 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 watsonx.data | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-36146, European organizations should implement the following specific measures: 1) Restrict and monitor access to IBM watsonx.data systems, ensuring that only necessary users have authentication credentials, and enforce the principle of least privilege to limit exposure. 2) Employ robust authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of credential compromise. 3) Monitor system logs and audit access to detect unusual or unauthorized attempts to retrieve system information. 4) Engage with IBM support channels to obtain patches or updates as soon as they become available, and apply them promptly. 5) Consider network segmentation and firewall rules to limit access to the watsonx.data platform from untrusted networks or users. 6) Conduct regular vulnerability assessments and penetration testing focused on information disclosure vectors to identify and remediate similar issues proactively. 7) Educate users with access about the risks of information leakage and enforce strict operational security policies. These steps go beyond generic advice by focusing on access control hardening, proactive monitoring, and vendor engagement specific to the IBM watsonx.data environment.
Description
IBM Lakehouse (watsonx.data 2.2) could allow an authenticated user to obtain sensitive server component version information which could aid in further attacks against the system.