EUVD-2026-85705
GHSA-c4xx-x56w-mpmp
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege DataStage user
-
DeliveryAccess exposed namespace file mounts
-
ExploitRead namespace-wide secrets
-
ExecutionHarvest credentials/tokens
-
ImpactPivot to adjacent workloads
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account (PR:L) on IBM DataStage on Cloud Pak for Data version 5.4.0.0 deployed on its OpenShift/Kubernetes substrate. The specific enabling condition is that namespace-scoped secrets are exposed through file mounts that are accessible to the DataStage workload/user - i.e. secret volumes mounted at the namespace level rather than scoped to the individual tenant. Limiting factors: exploitation is gated by valid authentication (not unauthenticated), impact is bounded to secrets present within the shared namespace, and it applies to the specific 5.4.0.0 build; there is no user-interaction requirement (UI:N). |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) rates this HIGH, but the signals are internally inconsistent: the description is a pure CWE-200 information-disclosure issue ('could allow a remote authenticated attacker to obtain sensitive information'), yet the vector claims full I:H and A:H integrity/availability impact. Reading arbitrary namespace-wide secrets does not by itself alter or destroy data, so the I:H/A:H components appear overstated for the described primary impact - verify with IBM whether the CVSS captures downstream compromise (stolen secrets reused to write/destroy) rather than the disclosure itself. Weighting the actual described behavior, this is a confidentiality-dominant flaw. No EPSS score, no CISA KEV listing, and no public POC are provided, so there is no evidence of active or widespread exploitation; combined with the low real-world footprint of this niche ETL product, this is a real-but-conditional issue (an authenticated tenant harvesting other workloads' secrets) rather than an internet-scale emergency. Priority should be driven by the fact that it exposes namespace-wide secrets - a credential-theft pivot - not by the raw 8.8. |
| Exploit ScenarioDerived | An attacker with valid low-privilege credentials to a DataStage tenant on Cloud Pak for Data reaches accessible file mounts inside the OpenShift/Kubernetes namespace and reads secret material (credentials, tokens, connection strings) belonging to other workloads sharing that namespace. Those harvested namespace-wide secrets are then reused to authenticate to and pivot into adjacent services. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Information disclosure in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated user to read sensitive data, because namespace-wide secrets are exposed through file mounts that are reachable from the DataStage workload. The vulnerability is rated CVSS 8.8 by the vendor, but our independent assessment re-scores it as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - a confidentiality-only issue with a scope change, reflecting that the exposed secrets belong to other tenants/services in the same Kubernetes/OpenShift namespace rather than to the vulnerable component itself; the source vector's claims of high integrity and availability impact are not supported by the CWE-200 description. Exploitation requires a valid authenticated account on the affected 5.4.0.0 build and no user interaction; there is no public exploit identified at time of analysis, and no EPSS or CISA KEV signal was provided. Organizations running this release should treat any credentials present in the affected namespace as potentially compromised.
RemediationAI
Apply the vendor fix referenced in IBM's advisory at https://www.ibm.com/support/pages/node/7288649; IBM lists a patch as available for the affected Cloud Pak for Data DataStage release, and the remediation should be scoped to the 5.4.0.0 build (patch available per vendor advisory - consult the support page for the exact target version, since input data does not name a specific fix build). Until the fix is deployed, treat every secret in the affected namespace as potentially disclosed: rotate service-account tokens, database credentials, API keys, and TLS material that were mounted into the DataStage namespace, and invalidate tokens issued to any service account whose secret was reachable. As compensating controls, set automountServiceAccountToken: false on workloads that do not call the Kubernetes API (trade-off: pods relying on in-cluster API access will break and need explicit token projection), tighten RBAC so DataStage service accounts cannot list, get, or watch secrets in the namespace (trade-off: may break operators or jobs that legitimately read secrets), move secrets to an external manager such as HashiCorp Vault or OpenShift's secrets-store CSI driver with per-workload scoping, and isolate DataStage into its own namespace or project with NetworkPolicy restrictions so cross-tenant secrets are never mounted alongside it (trade-off: namespace re-architecture may require redeployment and re-validation of pipelines). Monitor audit logs for unexpected secret reads or API calls originating from DataStage pods to detect exploitation attempts.
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 is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), realized in the Kubernetes/OpenShift substrate that hosts IBM DataStage on Cloud Pak for Data. In Kubernetes, secrets are commonly surfaced to pods either as environment variables or as projected/tmpfs file mounts; when secret volumes are mounted namespace-wide rather than scoped to the individual tenant or workload, any process (or user) with access to that workload can simply read the mounted files and recover credentials, tokens, connection strings, or certificates that were never intended for it. The CPE cpe:2.3:a:ibm:datastage_on_cloud_pak_for_data:*:*:*:*:*:*:*:* identifies the Cloud Pak for Data DataStage offering as the affected product family, with the vendor advisory narrowing the exposure to build 5.4.0.0. Because the leaked material typically includes service-account tokens, database credentials, or TLS key material belonging to other components in the same namespace, the assessed vector carries S:C (scope changed) - the vulnerable component affects resources beyond its own security authority - while impact remains C:H/I:N/A:N, i.e. read-only disclosure with no demonstrated ability to modify data or disrupt service.
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:N/A:N
Authenticated remote read of secrets → PR:L, C:H; described impact is disclosure only so I:N/A:N; theft of namespace-wide secrets belonging to other workloads crosses a security boundary → S:C.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to the exposure of namespace-wide secrets via accessible file mounts.
Executive ViewAI
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains an information-disclosure issue that can let an authenticated user read secrets belonging to other tenants or services in the same Kubernetes/OpenShift namespace. Because those secrets can include credentials used across the platform, leadership should treat this as a high-impact confidentiality and multi-tenant trust risk, even though there is no public exploit identified at time of analysis. Patch available per vendor advisory, so remediation urgency is driven by the potential for credential compromise, lateral movement, and compliance exposure.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Exploit-DB