CVE-2025-13691
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM DataStage on Cloud Pak for Data versions 5.1.2 through 5.3.0 contains an information disclosure vulnerability where sensitive information is returned in HTTP responses. This data could enable an attacker to impersonate other users in the system, likely through exposed session tokens, credentials, or user identity tokens.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.1.2, < 5.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check IBM DataStage versionLocate the installed version of IBM DataStage on Cloud Pak for Data through the Cloud Pak for Data administration console, or by querying the DataStage service version endpoint if available. Compare the installed version against the affected range: 5.1.2 through 5.3.0.Affected if The installed version is 5.1.2, 5.1.3, 5.2.0, 5.2.1, 5.2.2, 5.3.0, or any version >= 5.1.2 and < 5.3.1
-
Verify DataStage API network exposureDetermine if the DataStage API endpoints are accessible from networks outside the trusted internal environment. Review firewall rules, load balancer configurations, or Kubernetes network policies that govern access to DataStage services.Affected if DataStage API endpoints are reachable from untrusted networks or the internet
-
Inspect HTTP responses for sensitive dataCapture and examine HTTP responses from DataStage API calls using a web proxy or network traffic analysis tool. Look for session tokens, credentials, user identity tokens, or other authentication-related data embedded in response bodies, headers, or cookies.Affected if HTTP responses contain session tokens, credentials, user identity tokens, or other sensitive authentication data that should not be exposed
-
Check for user impersonation capabilityAnalyze whether the exposed sensitive information in HTTP responses could be extracted and reused to authenticate as other users in the system. Test with different user accounts if permitted.Affected if Extracted tokens or credentials from responses successfully authenticate as a different user
A user is affected if they run IBM DataStage on Cloud Pak for Data version 5.1.2 through 5.3.0 AND the DataStage API is network-accessible AND HTTP responses contain exposed authentication tokens or credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.3.1
Apply IBM's security patch for this vulnerability when available. In the interim, implement strict network access controls to limit exposure to the DataStage API endpoints and monitor for anomalous authentication patterns.
5.3.1
- Review IBM Cloud Pak for Data 5.3.1 release notes and documentation for any pre-upgrade requirements
- Ensure you have a complete backup of your current DataStage configuration and data
- Stop all DataStage jobs and services running on the Cloud Pak for Data instance
- Follow IBM's standard upgrade procedure for Cloud Pak for Data to update to version 5.3.1 or later
- After upgrade, verify that the HTTP response no longer contains sensitive information that could be used for user impersonation
- Test DataStage flows to ensure functionality is intact post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data