| CVE-2025-36145 |
IBM watsonx.data 2.2 through 2.3.1 IBM Lakehouse does not properly restrict inbound and outbound connections which could…
|
5.4
Medium
|
May 26, 2026 |
| CVE-2025-36180 |
IBM watsonx.data 2.2 through 2.3 IBM Lakehouse does not properly restrict communication between pods which could allow…
|
5.3
Medium
|
Apr 30, 2026 |
| CVE-2025-36183 |
IBM watsonx.data 2.2 through 2.2.1 IBM Lakehouse could allow a privileged user to upload malicious files that could be…
|
3.8
Low
|
Feb 17, 2026 |
| CVE-2025-36140 |
IBM watsonx.data 2.2 through 2.2.1 could allow an authenticated user to cause a denial of service through ingestion pods…
|
6.5
Medium
|
Dec 8, 2025 |
| CVE-2025-36144 |
IBM Lakehouse (watsonx.data 2.2) stores potentially sensitive information in log files that could be read by a local…
|
3.3
Low
|
Sep 27, 2025 |
| CVE-2025-36146 |
IBM Lakehouse (watsonx.data 2.2) could allow an authenticated user to obtain sensitive server component version…
|
4.3
Medium
|
Sep 18, 2025 |
| CVE-2025-36143 |
IBM Lakehouse (watsonx.data 2.2) could allow an authenticated privileged user to execute arbitrary commands on the…
|
4.7
Medium
|
Sep 18, 2025 |
| CVE-2025-36139 |
IBM Lakehouse (watsonx.data 2.2) is vulnerable to stored cross-site scripting
|
5.5
Medium
|
Sep 18, 2025 |