Skip to content
major vulnerability· requires attention

Authenticated remote command-injection RCE in IBM DataStage on Cloud Pak for Data — enterprise platform used broadly; high-impact for organizations running CP4D.

Applications

CVE-2026-82099

8.8
High
EPSS 0.44%Patch availableSep 12, 2026

Authenticated command-injection RCE in IBM DataStage on Cloud Pak for Data

common questions

Is CVE-2026-82099 being exploited?

Not confirmed. CVE-2026-82099 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. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2026-82099?

CVE-2026-82099 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-82099?

Yes. A fix has been recorded for CVE-2026-82099. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-82099 affect?

CVE-2026-82099 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-82099?

Apply vendor fixes/mitigations when available; restrict DataStage access, enforce least privilege, 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 OS commands => arbitrary code execution, host compromise, data theft and 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