Security readout for executives and security teams
Plain-English summary
IBM watsonx.data 2.2 and 2.3 (IBM Lakehouse) does not properly restrict communication between Kubernetes pods. An attacker with adjacent network access could move data between pods that should be isolated. Business risk is data integrity inside the analytics platform, not direct data theft or outage. Impact is moderate and contained to environments running affected versions.
Executive priority
Schedule a planned upgrade in the next maintenance window. This is not an emergency, but watsonx.data customers running 2.2 or 2.3 should track the IBM advisory and patch to preserve data integrity assurances inside analytics environments.
Technical view
CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints) in watsonx.data Lakehouse pod networking. CVSS 3.1 base 5.3 (AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) indicates adjacent-network attack with high complexity, no privileges or user interaction, and high integrity impact only. Missing east-west segmentation between pods could let an attacker on the cluster network alter or transfer data across pod boundaries.
Likely exposure
Limited to organizations running IBM watsonx.data versions 2.2.0 through 2.3.0 on Kubernetes-based Lakehouse deployments. Exploitation requires adjacent network position (same broadcast/cluster domain), which narrows exposure to attackers who already have a foothold in the cluster network or a co-tenant pod.
Exploitation context
No public reports of in-the-wild exploitation. Not listed in CISA KEV. CVSS attack complexity is high and access is adjacent, indicating exploitation is non-trivial and requires existing cluster network presence. No proof-of-concept is referenced in the IBM advisory or CVE record provided.
Researcher notes
Vector AV:A with AC:H limits practical reach; treat as a lateral-movement amplifier rather than an initial access bug. Confirm whether your environment relies on namespace-level isolation only versus enforced NetworkPolicies. The IBM advisory is the authoritative source for exact fixed versions and configuration guidance; the CVE record does not enumerate a specific patched build.
Mitigation direction
- Apply the fix per IBM Security Bulletin at ibm.com/support/pages/node/7270593.
- Upgrade watsonx.data Lakehouse to the IBM-recommended fixed release.
- Enforce Kubernetes NetworkPolicies to restrict pod-to-pod traffic to required flows only.
- Segment the cluster network and restrict adjacent access to watsonx.data namespaces.
- Monitor east-west traffic between watsonx.data pods for anomalous data transfers.
Validation and detection
- Inventory watsonx.data deployments and confirm version against the 2.2.0–2.3.0 affected range.
- Verify the IBM-published patch or fix level is applied per the vendor bulletin.
- Review NetworkPolicy resources in watsonx.data namespaces for default-deny baselines.
- Test pod-to-pod reachability from a non-privileged namespace to confirm intended restrictions.
- Check cluster audit and network flow logs for unexpected cross-pod connections.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-923: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-36180 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/7270593CVE reference · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Communication Channel to Intended Endpoints
Improper Restriction of Communication Channel to Intended Endpoints represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.