---
id: "CVE-2026-81212"
kind: "vulnerability"
aliases: ["CVE-2026-81212"]
title: "IBM DataStage on Cloud Pak for Data: unauthenticated write to shared Redis"
severity: "critical"
cvss: 10.0
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "DataStage on Cloud Pak for Data", "fixed": ["5.4 patch 8"], "affected": "5.4.0.0", "ecosystem": "vendor"}]
ecosystems: []
tags: ["cloud-pak-for-data", "ibm-datastage", "infrastructure", "multi-tenant", "redis", "self-hosted"]
not_affected_if: ["not-installed", "version-not-5.4.0.0"]
published_at: "2026-10-20T22:19:51+00:00"
first_seen_at: "2026-10-23T21:57:25+00:00"
updated_at: "2026-10-23T23:05:10+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-81212", "first_seen_at": "2026-10-23T21:57:25+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-23T23:05:10+00:00"}]
---

# IBM DataStage on Cloud Pak for Data: unauthenticated write to shared Redis

IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an unauthenticated network caller write arbitrary data into the shared Redis under any tenant's key. That can poison cached flow parameters and break the credential-encryption boundary across tenants. CVSS 10.0 (IBM), CWE-285. IBM's fix is 5.4 patch 8 or later, and it lists no workaround.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:DataStage on Cloud Pak for Data affected 5.4.0.0 fixed 5.4 patch 8

## How to check

Check whether DataStage is installed on your Cloud Pak for Data / Software Hub cluster and whether its version is 5.4.0.0 without 5.4 patch 8 applied (check the installed DataStage service version and patch level in the Software Hub/cpd-cli service listing). IBM gives no exploit-specific test. Until patched, restrict network access to the DataStage and shared Redis endpoints.

## Fix

Upgrade DataStage on Cloud Pak for Data to 5.4 patch 8 or later, following IBM's Software Hub 5.4.x instructions. IBM lists no workaround or mitigation. After patching, consider rotating connection credentials and reviewing cached flow parameters, since an attacker could have written to them.

## Timeline

- 2026-10-23T21:57:25+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-81212
- 2026-10-23T23:05:10+00:00 analyst — IBM bulletin node 7289603 (published 25 Sep 2026): 5.4.0.0 affected, fix is 5.4 patch 8 or later, IBM lists no workarounds. No exploitation or public PoC found (KEV no, EPSS <1%); no social discussion checked beyond web search. IBM gives no exact check command.

## Documents

- [advisory] IBM Security Bulletin: DataStage on Cloud Pak for Data has several vulnerabilities due to open source software (CVE-2026-81212) https://www.ibm.com/support/pages/node/7289603
- [describes] CVE.report: CVE-2026-81212 https://cve.report/CVE-2026-81212
- [fix] IBM Security Bulletin: DataStage on Cloud Pak for Data has several vulnerabilities due to open source software (CVE-2026-81212) https://www.ibm.com/support/pages/node/7289603

## From the sources

IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an unauthenticated user to perform an arbitrary write into shared Redis under any tenant's key. This collapses the platform's credential-encryption boundary and lets an anonymous caller poison any tenant's cached flow parameters.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_