Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-25926: IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 is vulnerable to an XML External E

37
Routine
MEDIUM 5.5UPGRADE

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

IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 247599.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score5.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance1.4% (top 28%)
CISA exploited listNo
WeaknessCWE-611
Published2024-02-29
Last modified2026-06-17
Publisher (CNA): IBM Corporation · Vendor: ibm

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

ibm security guardium key lifecycle manager UPGRADE
Affected: >= 3.0.0 and < 4.1.1.7
Fixed in: 4.1.1.7
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy security-guardium-key-lifecycle-manager || rpm -q security-guardium-key-lifecycle-manager || security-guardium-key-lifecycle-manager --version
2. UPGRADE to 4.1.1.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-guardium-key-lifecycle-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-guardium-key-lifecycle-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison security-guardium-key-lifecycle-manager sudo apt install security-guardium-key-lifecycle-manager=<VERSION_BEFORE_3.0.0> sudo apt-mark hold security-guardium-key-lifecycle-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-guardium-key-lifecycle-manager sudo dnf downgrade security-guardium-key-lifecycle-manager-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add security-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-2023-25926?

security guardium key lifecycle manager: upgrade to 4.1.1.7. Exact commands for each OS are on this page.

Is CVE-2023-25926 being exploited?

CVE-2023-25926 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-2023-25926 affect?

CVE-2023-25926 affects security guardium key lifecycle manager. Severity is medium (CVSS 5.5). IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive info

How urgent is CVE-2023-25926?

Priority 37/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.