CVE-2025-36180: CWE-923 Improper Restriction of Communication Channel to Intended Endpoints in IBM watsonx.data
IBM watsonx.data versions 2.2.0 through 2.3 have a vulnerability where communication between pods is not properly restricted. This flaw could allow an attacker to transfer data between pods without intended restrictions. The vulnerability is classified under CWE-923, indicating improper restriction of communication channels to intended endpoints. The CVSS score is 5.3, reflecting a medium severity level. No official patch or remediation guidance has been provided yet, and no known exploits are reported in the wild.
AI Analysis
Technical Summary
CVE-2025-36180 affects IBM watsonx.data versions 2.2.0 through 2.3, specifically the IBM Lakehouse component. The vulnerability arises from improper restriction of communication channels between pods, potentially allowing unauthorized data transfer between pods. This is categorized as CWE-923. The CVSS 3.1 base score is 5.3, with attack vector as adjacent network, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No patch or official remediation level has been disclosed by IBM as of the publication date.
Potential Impact
The vulnerability could allow an attacker to transfer data between pods without restrictions, potentially impacting data integrity within the affected environment. There is no reported impact on confidentiality or availability. The medium CVSS score reflects moderate risk due to the high attack complexity and the requirement for adjacent network access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official remediation level or patch links are provided, users should monitor IBM advisories for updates. Until a fix is available, limiting network access to pods and enforcing strict network segmentation may help reduce exposure, but these are general mitigations and not vendor-confirmed for this issue.
CVE-2025-36180: CWE-923 Improper Restriction of Communication Channel to Intended Endpoints in IBM watsonx.data
Description
IBM watsonx.data versions 2.2.0 through 2.3 have a vulnerability where communication between pods is not properly restricted. This flaw could allow an attacker to transfer data between pods without intended restrictions. The vulnerability is classified under CWE-923, indicating improper restriction of communication channels to intended endpoints. The CVSS score is 5.3, reflecting a medium severity level. No official patch or remediation guidance has been provided yet, and no known exploits are reported in the wild.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-36180 affects IBM watsonx.data versions 2.2.0 through 2.3, specifically the IBM Lakehouse component. The vulnerability arises from improper restriction of communication channels between pods, potentially allowing unauthorized data transfer between pods. This is categorized as CWE-923. The CVSS 3.1 base score is 5.3, with attack vector as adjacent network, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No patch or official remediation level has been disclosed by IBM as of the publication date.
Potential Impact
The vulnerability could allow an attacker to transfer data between pods without restrictions, potentially impacting data integrity within the affected environment. There is no reported impact on confidentiality or availability. The medium CVSS score reflects moderate risk due to the high attack complexity and the requirement for adjacent network access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official remediation level or patch links are provided, users should monitor IBM advisories for updates. Until a fix is available, limiting network access to pods and enforcing strict network segmentation may help reduce exposure, but these are general mitigations and not vendor-confirmed for this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- ibm
- Date Reserved
- 2025-04-15T21:16:23.419Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f3cb59cbff5d86108f882e
Added to database: 4/30/2026, 9:36:25 PM
Last enriched: 5/8/2026, 2:13:27 AM
Last updated: 6/15/2026, 10:29:20 AM
Views: 132
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.