Skip to content
major vulnerability· requires attention

Authenticated remote OS command injection in widely used IBM DataStage on Cloud Pak for Data; can disrupt enterprise data pipelines and enable lateral movement.

Applications

CVE-2026-81545

8.8
High
EPSS n/aSep 26, 2026

Authenticated remote OS command injection in IBM DataStage on Cloud Pak for Data.

common questions

Is CVE-2026-81545 being exploited?

Not confirmed. CVE-2026-81545 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-81545?

CVE-2026-81545 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-81545?

Not known from our data. No patch reference has been recorded for CVE-2026-81545, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-81545 affect?

CVE-2026-81545 affects IBM DataStage on Cloud Pak for Data 5.4.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-81545?

Restrict access, apply vendor patch when available, enforce least privilege and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM DataStage on Cloud Pak for Data 5.4.0.0
impact

Authenticated attacker can execute arbitrary OS commands as the service user, enabling data theft, pipeline disruption, or lateral movement.

action required

Immediate action required

affected versions
IBM DataStage on Cloud Pak for Data
  • affected5.4.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free