Quick answers
- Is CVE-2026-78537 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78537 being exploited in the wild.
- How severe is CVE-2026-78537?
- Medium severity, with a CVSS score of 6.8, published 8 November 2026.
- Which products and versions are affected?
- IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, 5.1.
- Is there a fix for CVE-2026-78537?
- Yes: fixed in 5.1.0-ISS-GKLM-FP0003. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78537 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-78537?
- Check whether you run IBM Guardium Key Lifecycle Manager 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.
How to fix
- Fixed in: 5.1.0-ISS-GKLM-FP0003
Technical details
The vulnerability stems from the use of a weak or broken cryptographic algorithm (CWE-327) in key material generation or protection. A local attacker with no privileges or user interaction required can exploit this to recover sensitive information. The issue affects multiple versions of the Guardium Key Lifecycle Manager running on Windows, Linux, and AIX platforms.
Affected products
- IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, 5.1
Timeline
- 2026-11-08: disclosed