IBM Guardium Key Lifecycle Manager versions 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 use a weak cryptographic algorithm that can allow a local attacker to extract sensitive information. The weakness is classified as CWE‑327, which indicates insecure cryptographic practices that may lead to downgrade or compromise of confidentiality. An attacker who can execute code or alter configuration locally may exploit this weakness and obtain data intended to be protected. The extent of the breach depends on the sensitivity of the stored keys and configuration but could potentially expose critical encryption keys used across the organization.

IBM Guardium Key Lifecycle Manager particularly versions 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 are impacted. These versions are listed in the common platform enumeration strings and are the primary focus of the advisory. There is no indication that earlier or later major releases are affected.

The vulnerability scores a CVSS metric of 6.8, placing it in the medium severity range. The EPSS score is currently unavailable, so the historical exploitation likelihood is unclear; however, since the issue requires local access, a privileged user or one who can elevate privileges locally is needed to exploit it. The advisory notes that the vulnerability is not listed in the CISA KEV catalog, suggesting no confirmed public exploits. Therefore, the risk is moderate, contingent on the presence of local users with sufficient privileges to interact with the Guardium Key Lifecycle Manager components.