Skip to main content
Menu
CVEs

IBM DataStage on Cloud Pak for Data information disclosure via path traversal in ETL component

Only affects DataStage on Cloud Pak for Data version 5.4.0.0. Fixed in 5.4 patch 8 or later.

CVE-2026-107331Published November 8, 2026, updated

9.9CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.4 patch 8 or later
Who is exposed
Specific setups only

Summary

The DataStage component of IBM Cloud Pak for Data has a flaw that lets a remote attacker with a low-privilege login read sensitive information through absolute-path traversal. The attack can be carried out over the network, and no user action is needed.

Written by a model

Original description

IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to an absolute-path traversal vulnerability.

Who should check

Teams running IBM DataStage on Cloud Pak for Data version 5.4.0.0 that need to upgrade to 5.4 patch 8 or later.

“DataStage on Cloud Pak for Data 5.4.0.0”

ibm.com

What to do

  1. Check whether your setup matches what the bug needs.

    Product is IBM DataStage on Cloud Pak for Data version 5.4.0.0.
  2. Upgrade to a fixed version: 5.4 patch 8 or later.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-107331 (DataStage on Cloud Pak for Data has several vulnerabilities), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-107331 (entry last updated 2026-11-12):
Affected:
- IBM DataStage on Cloud Pak for Data: versions 5.4.0.0
Fixed versions: 5.4 patch 8 or later.
Conditions (all must be true for the bug to be hit):
- Product is IBM DataStage on Cloud Pak for Data version 5.4.0.0. (source: https://www.ibm.com/support/pages/node/7294270)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-107331 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107331 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ibm.com/support/pages/node/7294270
- https://www.cve.org/CVERecord?id=CVE-2026-107331
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-107331
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107331"}.

Affected versions

cve.now Index

18of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.9/10CVSS 9.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now4 days
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 8Nov 22
  • EPSS: 0.51%
  • Posted on X by cve.now Nov 8

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 1

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchibm.com · support/pages/node/7294270
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-107331
RecordNVD · CVE-2026-107331

Questions about CVE-2026-107331

Is CVE-2026-107331 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A remote attacker who has valid credentials can obtain sensitive information through an absolute-path traversal flaw.

Source: ibm.com, cve.org

Which versions are affected by CVE-2026-107331?

DataStage on Cloud Pak for Data: version 5.4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory lists IBM DataStage on Cloud Pak for Data version 5.4.0.0. Compare the installed product version against that version to check the installed version.

Source: ibm.com, cve.org

How do I fix CVE-2026-107331?

Upgrade to 5.4 patch 8 or later by following IBM's instructions at https://www.ibm.com/docs/en/software-hub/5.4.x.

Source: ibm.com, cve.org

No corrections so far. Something wrong on this page? Report an error.