Datastage On Cloud Pak For Data EUVD-2026-77790

IBM DataStage deployments on Cloud Pak for Data 5.4.0.0 carry a high-severity OS command injection flaw that allows any user holding valid DataStage credentials to run arbitrary operating-system commands under the service account on the affected host or container. Because that account typically holds broad read/write access to data pipelines, credentials, and connected repositories, a single compromised or over-privileged user could silently corrupt, exfiltrate, or destroy regulated data and disrupt analytics and ETL workloads the business depends on. Leadership should care because the risk is concentrated in the platform that moves and transforms enterprise data, and the fix requires a coordinated platform upgrade rather than a routine endpoint action.

Within 24 hours, inventory every Cloud Pak for Data 5.4.0.0 instance running DataStage, confirm whether it is internet-reachable or shared with lower-trust users, and validate that DataStage service accounts follow least privilege with no access to unrelated host resources; simultaneously open a change request with IBM support to obtain the vendor fix and its exact build level. Within 7 days, apply the vendor patch to the highest-exposure and production DataStage environments first, restrict access to trusted identity sources, enforce MFA on all accounts that can reach DataStage, and enable audit logging on service-account command execution to detect anomalous child processes. Within 30 days, complete patching across all remaining Cloud Pak for Data 5.4.0.0 DataStage deployments, review and prune DataStage user entitlements, and add a recurring patch-compliance check so future CWE-78 exposures in this platform are remediated on a defined cadence.

Apply vendor patch.