CVE-2026-78537 · Vendor
NO FIX YET
IBM Guardium Key Lifecycle Manager versions 4.1 through 5.1 use a weak cryptographic algorithm. A local attacker can obtain sensitive information as a result.
first public Nov 8, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Organisations running IBM Guardium Key Lifecycle Manager versions 4.1, 4.1.1, 4.2, 4.2.1, 5.0 or 5.1. The attacker must have local access to the machine. The sources do not say which deployments are affected beyond the version range.
Not affected if version-outside-range
Who cares ibm-guardium-key-lifecycle-manager, self-hosted
No fix yet, per the sources.
IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 could allow a local attacker to obtain sensitive information due to the use of a weak cryptographic algorithm.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.