CVE-2025-13691

CVE-2025-13691 is a high-severity vulnerability in Ibm Datastage On Cloud Pak For Data with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-497.

Key facts

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.

Frequently asked questions

What is CVE-2025-13691?
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.
How severe is CVE-2025-13691?
CVE-2025-13691 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-13691 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-13691?
CVE-2025-13691 affects Ibm Datastage On Cloud Pak For Data. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-13691?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-13691 have an EU (EUVD) identifier?
Yes. CVE-2025-13691 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-207822.
When was CVE-2025-13691 published?
CVE-2025-13691 was published on 2026-02-17 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Datastage On Cloud Pak For Data

All CVEs affecting Ibm Datastage On Cloud Pak For Data →

Other CWE-497 vulnerabilities

Browse all CWE-497 vulnerabilities →