CVE-2025-36144: IBM watsonx.data · Sensitive Data in Logs
Affects IBM watsonx.dataSource CVE Database V5
Not known to be exploited · CVSS 3.3 Low.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM watsonx.data | Affected
| Fixed in– |
AI-suggested
European organizations should implement strict access controls on systems running IBM watsonx.data 2.2 to limit local user access only to trusted personnel. Log files should be stored with appropriate file permissions to prevent unauthorized reading. Organizations should audit and monitor log file contents regularly to detect any sensitive information leakage. Where possible, configure watsonx.data to minimize logging of sensitive data or enable log sanitization features if available. Employ host-based intrusion detection systems (HIDS) to alert on unusual access to log files. Additionally, organizations should stay updated with IBM advisories and apply patches or updates as soon as they become available. In the interim, consider isolating systems running vulnerable versions or deploying compensating controls such as encryption of log files at rest. Conduct regular security training to raise awareness about the risks of local access and data exposure through logs.
Description
IBM Lakehouse (watsonx.data 2.2) stores potentially sensitive information in log files that could be read by a local user.