CVE-2025-36180

Medium
5.3
0.05.010.0
Year
2026
Published
Apr 30, 2026
Known Affected Devices
0
CVSS Score
5.3

What is CVE-2025-36180?

IBM watsonx.data 2.2 through 2.3 IBM Lakehouse does not properly restrict communication between pods which could allow an attacker to transfer data between pods without restrictions.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
AV
Attack Vector
Adjacent

Exploitable from an adjacent network (e.g. same LAN, Wi-Fi segment, Bluetooth).

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
None

No authentication required. Any anonymous user can exploit this vulnerability.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
None

No confidentiality impact. Sensitive data is not exposed.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
None

No availability impact. Service remains fully operational.

FAQ

How severe is CVE-2025-36180?

CVE-2025-36180 has a CVSS score of 5.3/10, rated as Medium. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2025-36180?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2025-36180 scores 5.3/10 (Medium). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2025-36180?

The list of devices confirmed to be affected by CVE-2025-36180 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2025-36180?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.