# CVE-2026-78537: IBM Guardium Key Lifecycle Manager is affected by a security vulnerability

Status: published. Published: 2026-11-08. Updated: 2026-11-08.

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.

## Remediation

- fix: IBM encourages customers to update their systems promptly.

Principal Product and Version(s)Remediation/FixesIBM Guardium Key Lifecycle Manager (GKLM) v4.1

1. Download IBM Guardium Key Lifecycle Manager  https://www.ibm.com/docs/en/gklm/5.x?topic=software-download-instructions (source: CNA: ibm)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: ibm) — https://www.ibm.com/support/pages/node/7292031

## Affected products and versions

- IBM / Guardium Key Lifecycle Manager: 4.1 (affected); 4.1.1 (affected); 4.2 (affected); 4.2.1 (affected); 5.0 (affected); 5.1 (affected). Source: CNA: ibm

## Severity and prioritization

- CVSS 3.1: 6.8 (medium); CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N; source: CNA: ibm

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-327

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.ibm.com/support/pages/node/7292031 (CNA: ibm; vendor-advisory, patch)

## Provenance

- CNA: ibm: https://www.cve.org/CVERecord?id=CVE-2026-78537; retrieved 2026-11-08; source updated 2026-11-08

Revision: 0f183d9af64beea0ccd5bf4eff35fdb2e277ed10f6008c7a3e0d120804cffd50

Canonical: https://y2.dev/cve/CVE-2026-78537

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.