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.
CVE-2026-82103
CRITICALPre-NVD 9.69.6Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-13. A secondary CVSS source baseline 9.6; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.6Exploit: None knownExposed services: Not assessed
Upgrade to 5.4 patch 7 or later by following these instructions https://www.ibm.com/docs/en/software-hub/5.4.x (from the CVE record's solution, IBM Corporation) — apply it.
- CVSS v3
- 9.6
- EG Score
- 9.6CRITICALhigh confidence
- EG Risk
- 43EG Risk 43/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity96% × 45%The EG Score, 9.6 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: Upgrade to 5.4 patch 7 or later by following these instructions https://www.ibm.com/docs/en/software-hub/5.4.x (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 21st
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
Upgrade to 5.4 patch 7 or later by following these instructions https://www.ibm.com/docs/en/software-hub/5.4.x (from the CVE record's solution, IBM Corporation). Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (1)
Auto-updated Oct 12, 2026Fix named in the CVE record's solution (IBM Corporation).
Web page
Security Bulletin: DataStage on Cloud Pak for Data has several vulnerabilities
https://www.ibm.com/support/pages/node/7288649Vendor Advisories for CVE-2026-82103(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-13 16:25 UTCGHSA enrichmentGHSA-8cf2-44vp-jxp5 · GitHub severity CRITICAL · GitHub CVSS 9.6
- 2026-10-13 15:27 UTCEG score recompute
- 2026-10-13 15:27 UTCGHSA enrichmentGHSA-8cf2-44vp-jxp5 · GitHub severity CRITICAL · GitHub CVSS 9.6
- 2026-10-13 14:50 UTCEG score recompute
- 2026-10-13 14:50 UTCGHSA enrichmentGHSA-8cf2-44vp-jxp5 · GitHub severity CRITICAL · GitHub CVSS 9.6
- 2026-10-12 23:26 UTCEG score recompute
- 2026-10-12 22:41 UTCEG score recomputeFirst assessed: 9.6 CRITICAL
- 2026-10-12 22:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-82103?
CVE-2026-82103 is a critical-severity vulnerability; its CVE record was published on October 12, 2026. 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.
When was the CVE record for CVE-2026-82103 published?
The CVE record for CVE-2026-82103 was published on October 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-82103 actively exploited?
CVE-2026-82103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82103?
CVE-2026-82103 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82103?
The CVE record's solution for CVE-2026-82103, written by its CNA IBM Corporation, names the fix: "Upgrade to 5.4 patch 7 or later by following these instructions https://www.ibm.com/docs/en/software-hub/5.4.x ." The vendor advisories EchelonGraph has for CVE-2026-82103 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82103
Is Your Infrastructure Affected by CVE-2026-82103?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.