# CVE-2025-36180: Inadequate Pod Communication Restrictions, affects watsonx.data

> Attackers can transfer data between pods without restrictions due to inadequate communication controls in IBM watsonx.data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-842g-rrpf-rmq9

## What is CVE-2025-36180?

CVE-2025-36180 is a medium-severity missing authorization vulnerability in IBM watsonx.data, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

## Which versions are affected by CVE-2025-36180?

It affects 1 product.


Products: Ibm Watsonx.data.

## How do I fix CVE-2025-36180?

No fix has been published for CVE-2025-36180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-36180 being exploited?

There is no known exploitation of CVE-2025-36180 in the wild and no public exploit code.

## Other vulnerabilities in IBM watsonx.data

- [CVE-2025-36140](https://insights.sbomify.com/CVE-2025-36140/): IBM watsonx.data Denial of Service (medium 6.5)
- [CVE-2025-36335](https://insights.sbomify.com/CVE-2025-36335/): Vulnerabilities found (medium 6.2)
- [CVE-2025-36139](https://insights.sbomify.com/CVE-2025-36139/): IBM watsonx.data cross-site scripting (medium 5.5)
- [CVE-2025-36145](https://insights.sbomify.com/CVE-2025-36145/): Multiple Vulnerabilities in watsonx.data (medium 5.4)
- [CVE-2025-36143](https://insights.sbomify.com/CVE-2025-36143/): IBM watsonx.data command execution (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36180 and fix it if it is affected.

What it is: CVE-2025-36180 is a medium-severity missing authorization vulnerability in IBM watsonx.data, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36180 in the wild and no public exploit code.

Affected product: IBM watsonx.data. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-36180/ (Markdown: https://insights.sbomify.com/CVE-2025-36180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-36180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-36180
- OSV: https://osv.dev/vulnerability/CVE-2025-36180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-36180/
Summaries are generated and may contain mistakes; the official description above is the record.