CVE-2023-25926 is a medium severity flaw in IBM Security Guardium Key Lifecycle Manager 3.0 through 4.1.1. NVD calls it XML external entity injection (CVSS 5.5), while IBM bulletin 6964516 describes it as local privilege escalation (CVSS 6.4). Both point to v4.2 or fix pack 4.1.1 FP7.
What's affected
This entry has a real source conflict, so read it carefully. The NVD record describes CVE-2023-25926 as XML external entity injection, scored 5.5, weakness CWE-611, and ties it to IBM X-Force ID 247599. IBM Security Bulletin 6964516 lists CVE-2023-25926 as a flaw that could allow a local privileged user to escalate to a higher level of access, CVSS 6.4 with a local vector, and links X-Force ID 247633. The same bulletin lists the XXE problem under a different identifier, CVE-2023-25685, with a score of 5.5 and X-Force ID 247599.
So the record and IBM disagree on both the description and the severity: 5.5 versus 6.4. Both are medium. I cannot tell from the sources which one is a labelling error, so treat the product as exposed to both an XXE problem and a local escalation problem until IBM says otherwise.
On versions the sources agree: 3.0, 3.0.1, 4.0, 4.1 and 4.1.1 are affected, and the fixes are v4.2 and v4.1.1.7 (fix pack 4.1.1 FP7).
How to check if you're exposed
IBM Security Guardium Key Lifecycle Manager (GKLM) is an appliance style server application, so the version is read from the product itself. Open the GKLM web console, or follow IBM's documentation for your platform, and note the version and fix pack level. The record also lists AIX among the affected platforms, so the same applies to GKLM installations on that operating system.
Compare what you see against the bulletin:
- Versions 3.0, 3.0.1, 4.0, 4.1 and 4.1.1 are in the affected list.
- The fixes are GKLM v4.2, or fix pack 4.1.1 FP7 (version 4.1.1.7) on the 4.1.1 line.
I did not find a documented one line command in the sources I read, so I am not offering one. If you cannot see the fix pack level, ask your IBM administrator to read it from the console or from the install records.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- Treat this CVE and CVE-2023-25685 as one upgrade, since IBM fixes both in the same releases.
- Identify GKLM servers and their version and fix pack levels.
- Upgrade to v4.2 or apply fix pack 4.1.1 FP7.
- Restrict console and local shell access to named administrators.
- Ask IBM support which description applies if your audit needs an exact answer.
Why it matters
An XML external entity flaw appears when a parser accepts references to outside resources that the document author controls. The result can be disclosure of local files or resource exhaustion, which matches the NVD wording. A local privilege escalation is a different problem: a user with some rights gains more.
Because the sources differ, a scanner that uses NVD text and an auditor who reads the IBM bulletin may describe this CVE differently. That is worth knowing before you write a risk statement. The record does not flag CISA KEV, and neither source states exploitation.
Quick check
Which description is right?
The sources disagree. NVD says XXE at 5.5, IBM bulletin 6964516 says local privilege escalation at 6.4 and lists the XXE under CVE-2023-25685.
Does the conflict change the fix?
No. Both point to GKLM v4.2 or fix pack 4.1.1 FP7.
Sources
- IBM Security Bulletin 6964516
- IBM X-Force entry 247599 (referenced in the record; page needs JavaScript)
- Gold entry
Last reviewed: 19 October 2026.