CVE-2026-1726: IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 enables privilege escalation, allowing

Routine

MEDIUM 4.8REMOTEDOWNGRADE

CVE-2026-1726 is a medium-severity flaw (CVSS 4.8) affecting guardium key lifecycle manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 mechanism

Why this priority

Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-269
Published	2026-04-23
Last modified	2026-10-26

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-23 00:16 UTCPublished CVE record published
2026-10-26 00:10 UTCUpdated Record last modified

ibm guardium key lifecycle manager DOWNGRADE

Affected: 4.1.0 · 4.1.1 · 4.2.0 · 4.2.1 · 5.0.0 · 5.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.1.0

1. Check installed version

apt-cache policy guardium-key-lifecycle-manager || rpm -q guardium-key-lifecycle-manager || guardium-key-lifecycle-manager --version

2. No fixed release: DOWNGRADE to a release before 4.1.0 (Debian / Ubuntu)

apt-cache madison guardium-key-lifecycle-manager sudo apt install guardium-key-lifecycle-manager=<VERSION_BEFORE_4.1.0> sudo apt-mark hold guardium-key-lifecycle-manager

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list guardium-key-lifecycle-manager sudo dnf downgrade guardium-key-lifecycle-manager-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add guardium-key-lifecycle-manager

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-1726?

guardium key lifecycle manager: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-1726 being exploited?

CVE-2026-1726 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-1726 affect?

CVE-2026-1726 affects guardium key lifecycle manager. Severity is medium (CVSS 4.8). 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

How urgent is CVE-2026-1726?

Priority 24/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs