# CVE-2026-84418: DataStage on Cloud Pak for Data Improper Certificate Validation

> Man-in-the-middle attackers can intercept connections due to improper certificate validation, capturing IAM tokens to read and modify DataStage projects and assets.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-528j-3v52-48qw

## What is CVE-2026-84418?

CVE-2026-84418 is a high-severity vulnerability in Ibm Datastage on Cloud Pak for Data, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Ibm Datastage on Cloud Pak for Data.

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

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

## Is CVE-2026-84418 being exploited?

There is no known exploitation of CVE-2026-84418 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-84418 and fix it if it is affected.

What it is: CVE-2026-84418 is a high-severity vulnerability in Ibm Datastage on Cloud Pak for Data, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84418 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-84418/ (Markdown: https://insights.sbomify.com/CVE-2026-84418/index.md)
```

## Sources

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

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