Quick answers
- Is CVE-2026-13463 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13463 being exploited in the wild.
- How severe is CVE-2026-13463?
- High severity, with a CVSS score of 7.5, published 28 July 2026.
- Which products and versions are affected?
- IBM Cloud Pak System 2.3.5.0; IBM Cloud Pak System Software 2.3.5.0; IBM Cloud Pak System Software Suite 2.3.5.0; IBM Storage Protect Not specified.
- Is there a fix for CVE-2026-13463?
- A patch was published on 2026-07-28: Fix available in version 2.3.5.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13463 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-13463?
- Check whether you run IBM Cloud Pak System, IBM Cloud Pak System Software, IBM Cloud Pak System Software Suite or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
IBM Cloud Pak System is vulnerable to information disclosure due to the improper handling of credentials within its logging mechanisms. The vulnerability, originating in the IBM Storage Protect component, results in sensitive credentials being written in plain text to system log files (CWE-798). A local attacker with access to these log files can extract the credentials to gain unauthorized elevated access. While the CVSS vector provided by the vendor indicates a network attack vector, the descriptive text specifies a local attacker. The issue is addressed in IBM Cloud Pak System version 2.3.5.1.
Affected products
- IBM Cloud Pak System 2.3.5.0
- IBM Cloud Pak System Software 2.3.5.0
- IBM Cloud Pak System Software Suite 2.3.5.0
- IBM Storage Protect Not specified
Timeline
- 2026-07-09: disclosed: Initial publication by IBM
- 2026-07-28: advisory: NVD publication date
- 2026-07-28: patched: Fix available in version 2.3.5.1