Quick answers
- Is CVE-2025-36180 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-36180 being exploited in the wild.
- How severe is CVE-2025-36180?
- Medium severity, with a CVSS score of 5.3, published 30 April 2026.
- Which products and versions are affected?
- IBM Watsonx.Data 2.2 - 2.3.
- Is there a fix for CVE-2025-36180?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-36180 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2025-36180?
- Check whether you run IBM Watsonx.Data at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in IBM watsonx.data (IBM Lakehouse) due to improper restriction of communication channels between pods (CWE-923). The root cause is a misconfiguration in the network policies or inter-pod communication layer that fails to enforce intended endpoints. An attacker situated on the adjacent network could exploit this to transfer data between pods without restrictions. While the attack complexity is high and requires adjacent network access, it bypasses intended isolation boundaries. IBM has released versions 2.3.1 and CPD 5.3.1 to remediate this issue.
Affected products
- IBM watsonx.data 2.2 - 2.3
Timeline
- 2026-04-23: advisory: Initial publication by IBM
- 2026-04-30: disclosed: NVD publication date