# CVE-2026-81207: DataStage on Cloud Pak for Data has several vulnerabilities due to open source software

> Authenticated tenants can perform Server-Side Request Forgery to access internal services and read responses, exposing sensitive data in IBM DataStage on Cloud Pak for Data.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-g8f6-97x5-mw3c

## What is CVE-2026-81207?

CVE-2026-81207 is a high-severity server-side request forgery vulnerability in Ibm Datastage on Cloud Pak for Data, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM DataStage on Cloud Pak for Data 5.4.0.0 allows any authenticated tenant — with no project membership or role — fully controls scheme/host/port/path of an outbound fetch originating from a shared-infrastructure pod, and the WSDL body is reflected verbatim to the caller. The ds-canvas pod sits on the OpenShift overlay with reach to co-tenant services, in-cluster CP4D APIs, and link-local addresses. Scope is Changed, confidentiality High (response-reflecting), integrity Low (GET-only side-effects).

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-81207?

It affects 1 product.


Products: Ibm Datastage on Cloud Pak for Data.

## How do I fix CVE-2026-81207?

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

## Is CVE-2026-81207 being exploited?

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

## Other vulnerabilities in Ibm Datastage on Cloud Pak for Data

- [CVE-2026-16346](https://insights.sbomify.com/CVE-2026-16346/): DataStage on Cloud Pak for Data has several vulnerabilities (critical 9.9)
- [CVE-2026-16338](https://insights.sbomify.com/CVE-2026-16338/): DataStage on Cloud Pak for Data has several vulnerabilities due to open source software (critical 9.9)
- [CVE-2026-82101](https://insights.sbomify.com/CVE-2026-82101/): DataStage on Cloud Pak for Data Path Traversal (critical 9.6)
- [CVE-2026-82103](https://insights.sbomify.com/CVE-2026-82103/): DataStage on Cloud Pak for Data Information Disclosure (critical 9.6)
- [CVE-2026-82110](https://insights.sbomify.com/CVE-2026-82110/): DataStage on Cloud Pak for Data Path Traversal (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81207 and fix it if it is affected.

What it is: CVE-2026-81207 is a high-severity server-side request forgery vulnerability in Ibm Datastage on Cloud Pak for Data, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81207 in the wild and no public exploit code.

Affected product: Ibm Datastage on Cloud Pak for 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-2026-81207/ (Markdown: https://insights.sbomify.com/CVE-2026-81207/index.md)
```

## Sources

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

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