DATASTAGE ON CLOUD PAK FOR DATA · CVE-2026-107330 · Vendor
FIX → 5.4 patch 8 ✓ verified
IBM DataStage 5.4.0.0 on Cloud Pak for Data has a Server-Side Request Forgery flaw. A remote attacker with a valid account can make the server send requests to internal targets and obtain sensitive information.
first public Nov 8, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running self-managed IBM DataStage on Cloud Pak for Data 5.4.0.0 that have not applied 5.4 patch 8. An attacker needs a valid authenticated account (low privileges) and network access; they can make the server send requests to internal targets and read sensitive data (IBM CVSS 7.7, scope changed, high confidentiality impact). Deployments on other versions, or already on 5.4 patch 8 or later, can skip it.
Not affected if auth-required, other-versions, patched-5.4-patch-8
Who cares auth-required, cloud-pak-for-data, ibm-datastage, self-hosted
5.4.0.0 without 5.4 patch 8 or later is affected5.3.1.x: IBM's bulletin lists only 5.4.0.0 as affectedIBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to a Server-Side Request Forgery (SSRF) vulnerability.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 5.4 patch 8
Upgrade DataStage on Cloud Pak for Data 5.4.0.0 to 5.4 patch 8 or later, following IBM's upgrade instructions in the bulletin.