Description
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.
Published: 2026-04-30
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

IBM watsonx.data versions 2.2 through 2.3 do not enforce restrictions on communication between pods, enabling an attacker to transfer data freely between pods. This flaw can lead to unauthorized disclosure or exfiltration of sensitive information stored in one pod to another pod, potentially compromising confidentiality of data within the cluster. The weakness is identified as CWE‑923, reflecting insufficient validation of inter‑pod interactions.

Affected Systems

IBM watsonx.data, including all releases from 2.2.0 through 2.3.0 and any 2.3.x build. The vulnerability also applies to deployments of watsonx.data on IBM Cloud Pak for Data (CPD) version 5.3.1. Current production environments running any of these versions are therefore exposed.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. EPSS is not available, and the flaw is not listed in the CISA KEV catalog, suggesting there are currently no actively exploited incidents documented. However, the likely attack vector is a privileged or compromised user within the cluster who can target inter‑pod traffic; such an adversary could craft traffic between pods to move data without restriction. The absence of external triggers makes exploitation unlikely from the outside, but any internal user with sufficient access could exploit this weakness. Applying the vendor’s patch remains the most effective mitigation.

Generated by OpenCVE AI on May 1, 2026 at 04:52 UTC.

Remediation

Vendor Solution

The product needs to be installed or upgraded to the latest available level watsonx.data 2.3.1 or watsonx.data on CPD 5.3.1.  Installation/upgrade instructions can be found here: https://www.ibm.com/docs/en/software-hub/5.3.x?topic=watsonxdata-installing


OpenCVE Recommended Actions

  • Upgrade to IBM watsonx.data 2.3.1 or IBM watsonx.data on CPD 5.3.1 following the installation/upgrade instructions provided by IBM.
  • Configure Kubernetes NetworkPolicy objects (or equivalent) to explicitly allow pod-to-pod communication only between authorized pods, thereby restoring isolation.
  • Verify cluster security controls and monitor pod network traffic for unapproved communication patterns, applying least‑privilege access controls to cluster accounts to prevent misuse by privileged users.

Generated by OpenCVE AI on May 1, 2026 at 04:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 01 May 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 30 Apr 2026 23:15:00 +0000

Type Values Removed Values Added
First Time appeared Ibm watsonx.data
Vendors & Products Ibm watsonx.data

Thu, 30 Apr 2026 22:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:ibm:watsonxdata:2.2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:watsonxdata:2.3:*:*:*:*:*:*:*

Thu, 30 Apr 2026 21:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Inadequate Pod Communication Restrictions, affects watsonx.data
First Time appeared Ibm
Ibm watsonxdata
Weaknesses CWE-923
CPEs cpe:2.3:a:ibm:watsonxdata:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:watsonxdata:2.2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:watsonxdata:2.3.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:watsonxdata:2.3:*:*:*:*:*:*:*
Vendors & Products Ibm
Ibm watsonxdata
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}


Subscriptions

Ibm Watsonx.data Watsonxdata
cve-icon MITRE

Status: PUBLISHED

Assigner: ibm

Published:

Updated: 2026-05-01T16:37:49.064Z

Reserved: 2025-04-15T21:16:23.419Z

Link: CVE-2025-36180

cve-icon Vulnrichment

Updated: 2026-05-01T16:37:44.895Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-04-30T22:16:24.737

Modified: 2026-05-01T15:27:15.287

Link: CVE-2025-36180

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-01T05:00:12Z

Weaknesses