Skip to content
major vulnerability· requires attention

Affects IBM Cloud Pak for Data, a widely deployed enterprise data platform; info disclosure across deployments could impact many organizations.

Cloud

CVE-2026-17467

8.2
High
EPSS n/aSep 17, 2026

Weak/deprecated cryptography in IBM Cloud Pak for Data System allows remote information disclosure.

common questions

Is CVE-2026-17467 being exploited?

Not confirmed. CVE-2026-17467 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.

How severe is CVE-2026-17467?

CVE-2026-17467 is rated High with a CVSS score of 8.2. 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-17467?

Not known from our data. No patch reference has been recorded for CVE-2026-17467, 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-17467 affect?

CVE-2026-17467 affects IBM Cloud Pak for Data System (Yosemite 1.0) 3.0.5.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17467?

Disable deprecated ciphers, enforce TLS≥1.2, apply vendor mitigations and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Cloud Pak for Data System (Yosemite 1.0) 3.0.5.2
impact

Remote attackers can exploit weak/deprecated crypto to obtain sensitive information (information disclosure).

action required

Immediate action required

affected versions
IBM Cloud Pak for Data System (Yosemite 1.0)
  • affected3.0.5.2

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free