Safeguard
Vulnerability Analysis•

CVE-2026-82093: High Unsafe Deserialization in IBM DataStage CP4D

IBM DataStage on Cloud Pak for Data 5.4.0.0 has an unsafe deserialization flaw giving code execution to a logged in user. Upgrade to 5.4 patch 7 or later.

Safeguard Security Team
3 min read

CVE-2026-82093 is a high severity (CVSS 8.8) unsafe deserialization flaw in IBM DataStage on Cloud Pak for Data 5.4.0.0. A remote authenticated attacker can execute arbitrary code. IBM's bulletin says to upgrade to 5.4 patch 7 or later and lists no workaround.

What's affected

The record, and IBM's bulletin, list one affected release: IBM DataStage on Cloud Pak for Data 5.4.0.0. The bulletin covers many issues at once, and this CVE is one entry in it.

IBM's remediation is to upgrade to 5.4 patch 7 or later, following the instructions linked from the bulletin. The bulletin lists no workarounds or mitigations, so patching is the only listed route. The bulletin's change history shows an initial publication in September 2026, while the record's published date is later, so the dates in the record and the bulletin do not match. That does not change the fix.

How to check if you're exposed

Find out which DataStage release each Cloud Pak for Data environment runs. In the Cloud Pak for Data web console, the service catalogue or the instances page lists the installed DataStage version. If your platform team uses the command line, the Cloud Pak for Data CLI can list installed services and their versions. The exact commands depend on your install, so use the IBM instructions linked from the bulletin.

Compare what you find with the bulletin. Version 5.4.0.0 without patch 7 is in scope. Also note who holds a login, because the record says a remote authenticated attacker is required. Any account that can reach DataStage, including service accounts and shared project users, counts.

What to do now

  1. Read the IBM bulletin and note which fix level your environments need. IBM lists upgrading to 5.4 patch 7 or later.
  2. Schedule the upgrade through your normal change process, starting with environments that hold production data pipelines.
  3. Review accounts with DataStage access and remove users and service accounts that no longer need it.
  4. Limit network access to the Cloud Pak for Data console to the networks your teams actually use.
  5. After patching, confirm the version in the console and record it for your vulnerability tracker.

Why it matters

Unsafe deserialization, tracked as CWE-502, means the program rebuilds objects from data that someone else controls. Depending on the format and the classes available, the rebuilding step can run code. IBM's description is brief and does not say which interface is affected, so treat the detail as unconfirmed beyond what the bulletin says.

The score of 8.8 reflects network access, low attack complexity, a low privilege requirement and full impact on confidentiality, integrity and availability. DataStage moves and transforms business data, so a code execution foothold in the platform is a serious position. The record does not list this CVE as exploited in the wild.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does the attacker need an account?

Yes. The record says remote authenticated attacker, which means any valid login to the platform.

Is there a workaround?

IBM's bulletin lists none. The listed remedy is the patch.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.