Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with valid DataStage credentials
-
DeliverySubmit request with crafted file path
-
ExploitBypass path validation (CWE-73)
-
ExecutionWrite arbitrary file to server
-
PersistOverwrite config/script for code execution
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
|
| Exploitation Conditions | Exploitation requires valid authenticated access to IBM DataStage on Cloud Pak for Data 5.4.0.0 (PR:L), after which the attacker abuses improper validation of user-supplied file paths (CWE-73) to write files to arbitrary locations. No user interaction is needed (UI:N) and the attack is network-reachable (AV:N) with low complexity (AC:L). The primary limiting factor is the authentication barrier - only principals who already possess DataStage credentials can reach the vulnerable path-handling logic; the exact feature or endpoint performing the write is not specified in available data, so the precise request prerequisite cannot be named from the input. |
| Impact | Signals are moderate and internally consistent, pointing to a real-but-not-urgent priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity attack that requires authentication (PR:L), and SSVC classifies Technical Impact as 'total' - matching the C:H/I:H/A:H claim since an arbitrary file write can corrupt configuration or code to achieve full compromise. However, SSVC also reports Exploitation: none and Automatable: no, and EPSS is low at 0.61% (48th percentile), indicating no observed exploitation and no mass-scanning trend. There is no CISA KEV listing and no public POC identified. The authentication requirement (PR:L) is the key mitigating factor: an attacker must already hold valid DataStage credentials, which limits this to insider-style or post-compromise abuse rather than opportunistic internet-wide attacks. Net assessment: patch on a normal prioritized schedule (elevated because impact is total and a vendor patch exists), but this is not a drop-everything emergency given low EPSS, no KEV, and the authentication barrier. Note a minor data inconsistency: the input Tags label this 'Information Disclosure,' but CWE-73 and the description describe an arbitrary file WRITE (integrity/availability), not disclosure - verify tagging. |
| Exploit ScenarioDerived | A remote attacker holding valid, low-privileged DataStage credentials on Cloud Pak for Data 5.4.0.0 submits a request containing a crafted file path that bypasses path validation (CWE-73), writing attacker-controlled content to an arbitrary location on the server. By overwriting a configuration file, script, or deployable artifact, the attacker can escalate to code execution and full system compromise. No public exploit code has been identified at the time of analysis, and no user interaction is required (UI:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 06, 2026
Arbitrary file write in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote, authenticated attacker to write files to attacker-chosen locations on the underlying host because user-supplied file paths are not properly validated (CWE-73). Exploitation requires valid DataStage credentials (CVSS PR:L, unauthenticated access is not sufficient) but no user interaction and no special conditions, and a successful write has high confidentiality, integrity, and availability impact, giving a base score of 8.8. No public exploit code has been identified at time of analysis, EPSS is 0.61% (48th percentile), and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so this is a real-but-not-urgent priority rather than an emergency.
Earlier versions of this analysis (1)
Authenticated arbitrary file write in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker who already holds valid DataStage credentials to write files to attacker-chosen locations on the server, because a feature that accepts a file path fails to properly validate it. The vendor scores this 9.9, but our independent assessment rates it as a scope-unchanged high-severity issue (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H), since the attacker must already be authenticated and the immediate confidentiality impact is limited although integrity and availability can be fully compromised. There is no evidence of active exploitation: CISA's SSVC rates exploitation as 'none', EPSS is low at 0.61% (48th percentile), and no public exploit code has been identified at time of analysis. A vendor patch is available per IBM's advisory.
RemediationAI
IBM has published a fix for this issue; the vendor advisory at https://www.ibm.com/support/pages/node/7286562 documents the patched level, and the input data confirms patch availability without naming an exact fix version, so treat the advisory as the source of truth for the precise build to install rather than assuming a version number. Update IBM DataStage on Cloud Pak for Data 5.4.0.0 to the fix level listed in that advisory (for Cloud Pak for Data, this is typically applied as a service/fix pack or by upgrading the DataStage operand to the corrected release). Where patching cannot be completed immediately, compensating controls should target the authentication barrier and the file-write surface: audit and aggressively minimize the set of accounts holding DataStage credentials, since every authenticated principal can reach the vulnerable path logic and low-privilege users are sufficient per the PR:L vector; restrict network access to the DataStage service and its management interfaces to trusted administrative networks, accepting the operational cost of breaking remote developer and job-scheduling workflows; and monitor or alert on unexpected file creation outside expected DataStage work directories, with the caveat that such monitoring is detective rather than preventive and generates noise in environments with many legitimate job-generated files. Because the vulnerable endpoint is not identified in the available data, no reliable feature-disable or endpoint-blocking workaround can be prescribed from this input. Note that CISA SSVC rates this as not automatable and no exploitation activity has been observed, so remediation can be scheduled through normal patch cycles rather than treated as an emergency.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-73 (External Control of File Name or Path): DataStage server-side logic accepts a file path that originates from user-supplied input and passes it to a file-write operation without canonicalization, allow-listing, or confinement to a designated directory. The affected component is IBM DataStage running as part of Cloud Pak for Data, an ETL/data-integration platform whose jobs, configuration, and supporting scripts live on the same filesystem that the vulnerable write routine can reach; that co-location is what elevates a path-handling bug from a data-integrity issue to a potentially total-impact one, since an attacker who can choose the destination path could target files that are later read or executed by the platform. The CPE entry cpe:2.3:a:ibm:datastage_on_cloud_pak_for_data:*:*:*:*:*:*:*:* is version-wildcarded, but the EUVD record and the vendor advisory scope the known-affected release to 5.4.0.0. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U) indicates the vulnerable path-handling logic is network-reachable and can be driven by any principal holding DataStage credentials, with no browser-style interaction and no scope change - but the specific feature, API, or job parameter that performs the write is not identified in the available data, so the exact request prerequisite cannot be named from the input.
Know when Datastage On Cloud Pak For Data gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable (AV:N), low complexity (AC:L), requires authentication (PR:L); arbitrary file write enables config/code overwrite yielding total compromise, so C/I/A all High.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
IBM DataStage on Cloud Pak for Data 5.4.0.0 IBM DataStage could allow a remote authenticated attacker to perform an arbitrary file write due to improper validation of file paths.
Executive ViewAI
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains an arbitrary file write flaw that lets anyone holding a valid DataStage account place files in locations of their choosing on the underlying host, which can undermine the confidentiality, integrity, and availability of the platform and anything running alongside it. Because the platform typically sits at the center of enterprise data pipelines and moves regulated or business-critical data, a successful exploit could mean tampered or exposed data and disrupted integration workloads. Exploitation is not currently observed and requires legitimate credentials, so leadership should treat this as a scheduled remediation priority rather than an emergency.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Arbitrary file read, write, and delete on IBM DataStage on Cloud Pak for Data 5.4.0.0 is possible for an authenticated l
Authenticated OS command execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets a remote attacker with a valid ac
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid pla
Denial of service in IBM DataStage on Cloud Pak for Data 5.4.0.0 can be triggered by a remote user who already holds val
Improper authentication in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated (low-privileged) at
Arbitrary file creation in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker to write f
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets a remote authenticated attacker with a low-priv
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker holding only
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an authenticated remote attacker with only low-
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an authenticated remote attacker holding low-
IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker with low privileges to execute arbitr
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an authenticated remote user execute arbitrary
EUVD-2026-77797
GHSA-9p83-pgmg-hprg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB