Affects IBM DataStage on Cloud Pak for Data, a widely used enterprise data platform; namespace-wide secret exposure can enable broad credential theft and lateral compromise.
CVE-2026-80423
Authenticated access exposes namespace-wide secrets via file mounts.
Is CVE-2026-80423 being exploited?
Not confirmed. CVE-2026-80423 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-80423?
CVE-2026-80423 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-80423?
Not known from our data. No patch reference has been recorded for CVE-2026-80423, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-80423 affect?
CVE-2026-80423 affects IBM DataStage on Cloud Pak for Data 5.4.0.0, IBM Cloud Pak for Data deployments using DataStage file mounts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-80423?
Follow IBM advisory; restrict file-mount access, rotate any exposed secrets, and apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote authenticated attacker can read namespace secrets (tokens/credentials) via mounts, enabling credential theft, lateral movement, and data exfiltration.
Immediate action required
- affected5.4.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.