CVE-2026-82103 — DataStage on Cloud Pak for Data Information Disclosure
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to an exposure of sensitive information to an unauthorized actor.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.ibm.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ibm Datastage On Cloud Pak For Data).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Ibm | Datastage On Cloud Pak For Data | version 5.4.0.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Ibm | Datastage On Cloud Pak For Data | version 5.4.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.6 | CVSS 3.1 | Critical | 3.1 | 5.8 | psirt@us.ibm.com via NIST National Vulnerability Database |
| 9.6 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.6 | CVSS 3.1 | Critical | — | — | ibm via CVE Program (cve.org) e CISA ADP |
| 6.5 | CVSS 3.1 | Medium | 2.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.30%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for anomalous data read/export volumes and access to sensitive records.
Analysis and videos
CVE-2026-82103: IBM DataStage on Cloud Pak for Data Sensitive Information Exposure
CVE-2026-82103 is a sensitive information exposure issue (CWE-200) in IBM DataStage on Cloud Pak for Data version 5.4.0.0, which the CNA rates as critical with a CVSS 3.1 base score of 9.6. The sources consulted describe a remote attacker with low-privilege authentication who could obtain sensitive information. No confirmed exploitation appears in the sources consulted, and the record does not list fixed versions, so administrators should check the IBM vendor bulletin directly.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · ibm/datastage on cloud pak for data
- CVSS changed · 9.6 → 6.5
- Source status changed · Undergoing Analysis → Analyzed
- Source status changed · Awaiting Analysis → Undergoing Analysis
- Affected products added · ibm/datastage on cloud pak for data
- SSVC assessment updated
- Source status changed · Received → Awaiting Analysis
- Record published
- CVSS changed · 9.6
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-84418 DataStage on Cloud Pak for Data Improper Certificate Validation 2d
- Critical CVE-2026-82110 DataStage on Cloud Pak for Data Path Traversal 2d
- High CVE-2026-82108 DataStage on Cloud Pak for Data Code Injection 2d
- High CVE-2026-82096 DataStage on Cloud Pak for Data Command Injection 2d
- Critical CVE-2026-82101 IBM DataStage on Cloud Pak for Data path traversal denial of service 2d
- High CVE-2026-82094 DataStage on Cloud Pak for Data has several vulnerabilities 21d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-82103 is "DataStage on Cloud Pak for Data Information Disclosure", rated Medium. It affects Datastage On Cloud Pak For Data (Ibm); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.