{"id":"CVE-2026-78537","aliases":[],"cve":{"records":[{"id":"CVE-2026-78537","source":"ibm","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-08-24T17:33:44.955Z","published":"2026-11-08T18:39:50.259Z","modified":"2026-11-09T14:10:58.185Z"}],"publishers":[{"name":"ibm","role":"CNA","organizationId":"9a959283-ebb5-44b6-b705-dcc2bbced522","modified":"2026-11-08T18:39:50.259Z"},{"name":"CISA-ADP","role":"ADP","organizationId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","modified":"2026-11-09T14:10:58.185Z"}],"references":[{"url":"https://www.ibm.com/support/pages/node/7292031","tags":["vendor-advisory","patch"],"source":"ibm"}],"weaknesses":[{"id":"CWE-327","description":"CWE-327 Use of a Broken or Risky Cryptographic Algorithm","source":"ibm"}],"applicability":[],"prioritization":[{"source":"CISA-ADP","type":"SSVC","role":"CISA Coordinator","timestamp":"2026-11-09T14:10:49.135086Z","decisions":[{"name":"Exploitation","value":"none"},{"name":"Automatable","value":"no"},{"name":"Technical Impact","value":"partial"}]}]},"title":"IBM Guardium Key Lifecycle Manager is affected by a security vulnerability","titleSource":"ibm","descriptionSource":"ibm","description":"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.","score":6.8,"severity":"medium","published":"2026-11-08T18:39:50.259Z","modified":"2026-11-09T14:10:58.185Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"IBM","name":"Guardium Key Lifecycle Manager","platforms":[],"versions":[{"version":"4.1","status":"affected"},{"version":"4.1.1","status":"affected"},{"version":"4.2","status":"affected"},{"version":"4.2.1","status":"affected"},{"version":"5.0","status":"affected"},{"version":"5.1","status":"affected"}],"cpes":["cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.1:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.1.0:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.1.1:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.2:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.2.0:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:4.2.1:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:5.0:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:5.0.0:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:5.1:*:*:*:*:*:*:*","cpe:2.3:a:ibm:guardium_key_lifecycle_manager:5.1.0:*:*:*:*:*:*:*"],"source":"ibm","url":"https://www.cve.org/CVERecord?id=CVE-2026-78537"}],"remediation":[{"text":"IBM encourages customers to update their systems promptly.\n\nPrincipal Product and Version(s)Remediation/FixesIBM Guardium Key Lifecycle Manager (GKLM) v4.1\n\n1. Download IBM Guardium Key Lifecycle Manager  https://www.ibm.com/docs/en/gklm/5.x?topic=software-download-instructions","source":"ibm","url":"https://www.cve.org/CVERecord?id=CVE-2026-78537"}],"references":["https://www.ibm.com/support/pages/node/7292031"],"sources":[{"name":"CVE","id":"CVE-2026-78537","modified":"2026-11-09T14:10:58.185Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-78537"}],"assessments":[{"source":"ibm","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","score":6.8}],"sourceAffected":[],"observedAt":"2026-11-09T14:21:42.517Z","kev":{"status":"not-listed","checkedAt":"2026-11-15T03:35:31.150Z"},"coverage":[{"source":"NVD","status":"no-result","checkedAt":"2026-11-08T18:55:41.834Z","attemptedAt":"2026-11-08T18:55:41.834Z"},{"source":"GHSA","status":"no-result","checkedAt":"2026-11-08T18:55:41.164Z","attemptedAt":"2026-11-08T18:55:41.164Z"},{"source":"EUVD","status":"no-result","checkedAt":"2026-11-08T18:55:43.278Z","attemptedAt":"2026-11-08T18:55:43.278Z"},{"source":"EPSS","status":"no-result","checkedAt":"2026-11-08T18:55:41.820Z","attemptedAt":"2026-11-08T18:55:41.820Z"}],"evidence":[],"aiSummary":{"text":"IBM Guardium Key Lifecycle Manager versions 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 may allow a local attacker to obtain sensitive information due to a weak cryptographic algorithm. The product uses a broken or risky cryptographic algorithm. A local attacker could exploit this weakness.","model":"@cf/meta/llama-3.3-70b-instruct-fp8-fast","generatedAt":"2026-11-08T18:51:12.976Z","sources":[{"name":"CVE","url":"https://www.cve.org/CVERecord?id=CVE-2026-78537"}]}}