Inadequate Pod Communication Restrictions, affects watsonx.data
Priority LOW 32CWE-923Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00186 8th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-36180
- 2026-10-03 Alias added: GHSA-842g-rrpf-rmq9
References
More IBM Watsonx.data vulnerabilities
- TI-2025-24722 IBM watsonx.data command execution CVSS 3.1HIGH 7.2
- TI-2025-24721 IBM watsonx.data Denial of Service CVSS 3.1MEDIUM 6.5
- TI-2025-24795 Vulnerabilities found CVSS 3.1MEDIUM 6.2
- TI-2025-24724 Multiple Vulnerabilities in watsonx.data CVSS 3.1MEDIUM 5.4
- TI-2025-24723 IBM watsonx.data information disclosure CVSS 3.1MEDIUM 5.5
- TI-2025-24720 IBM watsonx.data cross-site scripting CVSS 3.1MEDIUM 5.5
Sources
- CVE-2025-36180 · CVE Program
- CVE-2025-36180 · NVD
- FIRST EPSS
- GHSA-842g-rrpf-rmq9 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences