VulnerabilityPublished 3 Mar 2026Updated 4 Mar 2026

CVE-2025-13616: 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

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: There is no loss of integrity within 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 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

To mitigate CVE-2025-13616, organizations should implement the following specific measures: 1) Restrict network access to IBM DataStage on Cloud Pak for Data interfaces to trusted users and systems only, minimizing exposure to unauthorized actors. 2) Conduct thorough audits of HTTP responses from the affected versions to identify and block leakage of sensitive information using web application firewalls or custom filtering rules. 3) Enforce strict role-based access controls (RBAC) to limit privileges and reduce the risk of exploitation by low-privilege users. 4) Monitor logs and network traffic for unusual access patterns or reconnaissance attempts that may indicate exploitation attempts. 5) Stay updated with IBM security advisories and apply patches or updates as soon as they become available, even though no patches are currently listed. 6) Consider deploying additional security layers such as encryption of sensitive data in transit and at rest, and segmentation of critical systems to limit lateral movement. 7) Educate administrators and security teams about the nature of the vulnerability to ensure prompt detection and response.

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 in further attacks against the system.

Impact

The primary impact of CVE-2025-13616 is the unauthorized disclosure of sensitive system information, which can significantly aid attackers in reconnaissance activities. This information can reveal system configurations, internal endpoints, or security mechanisms, enabling attackers to identify weaknesses or plan more effective attacks such as privilege escalation or lateral movement. Although the vulnerability does not directly compromise data integrity or system availability, the confidentiality breach can lead to broader security incidents if leveraged effectively. Organizations relying on IBM DataStage on Cloud Pak for Data for critical data processing and integration could face increased risk of targeted attacks, data breaches, or operational disruptions stemming from subsequent exploits. The medium severity rating suggests a moderate but non-trivial risk, particularly in environments where attackers can gain initial low-level access.

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/7261771 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Mar 2026, 20:11 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats