VulnerabilityPublished 17 Feb 2026Updated 26 Feb 2026

CVE-2025-13691: IBM DataStage on Cloud Pak for Data · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM DataStage on Cloud Pak for DataSource CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMDataStage on Cloud Pak for Data	Affected >=5.1.2 <=5.3.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:datastage_on_cloud_pak_for_data:5.1.2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:datastage_on_cloud_pak_for_data:5.3.0:*:*:*:*:*:*:*

AI-suggested

Organizations should immediately assess their IBM DataStage on Cloud Pak for Data deployments to identify affected versions (5.1.2 through 5.3.0). Although no official patches are listed, it is critical to monitor IBM security advisories for forthcoming updates and apply them promptly once available. In the interim, restrict network access to the DataStage management interfaces using network segmentation, firewalls, and VPNs to limit exposure to trusted users only. Implement strict access controls and multi-factor authentication to reduce the risk of unauthorized access. Conduct thorough audits of user privileges and session management to detect and prevent impersonation attempts. Employ web application firewalls (WAFs) to detect anomalous HTTP responses and block suspicious activities. Additionally, monitor logs for unusual authentication or access patterns indicative of exploitation attempts. Educate administrators and users about the risks and ensure rapid incident response capabilities are in place.

Description

IBM DataStage on Cloud Pak for Data 5.1.2 through 5.3.0 returns sensitive information in an HTTP response that could be used to impersonate other users in the system.

Impact

The vulnerability could lead to unauthorized disclosure of sensitive information, enabling attackers to impersonate legitimate users and access or manipulate critical data integration workflows. This compromises confidentiality and integrity of enterprise data, potentially leading to data breaches, regulatory non-compliance, and operational disruptions. Organizations relying on IBM DataStage for critical ETL and data orchestration tasks may face significant risks including exposure of proprietary or personal data, loss of data integrity, and erosion of trust in data governance. The absence of impact on availability means systems remain operational but compromised. The ease of exploitation and network accessibility increase the likelihood of targeted attacks, especially in environments where multiple users share access or where credentials are reused or weak. The vulnerability could also facilitate further attacks within the network by enabling impersonation and privilege escalation.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7259956 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 27 Feb 2026, 08:11 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats