Safeguard
Vulnerability Analysis•

CVE-2023-25922: Medium File Upload Flaw in IBM Guardium GKLM

CVE-2023-25922 is a medium severity dangerous file type upload flaw in IBM Guardium Key Lifecycle Manager 3.0 to 4.1.1. Upgrade to 4.2 or 4.1.1 FP7.

Safeguard Security Team
4 min read

CVE-2023-25922 is a medium severity (CVSS 4.3) dangerous file type upload flaw in IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1 and 4.1.1. IBM says it is fixed in v4.2 and fix pack 4.1.1 FP7, so upgrade to one of those releases.

What's affected

The record and IBM Security Bulletin 6964516 both list GKLM 3.0, 3.0.1, 4.0, 4.1 and 4.1.1 as affected. IBM says the fixes are in GKLM v4.2 and v4.1.1.7, and recommends upgrading to v4.2 or applying the latest fix pack, 4.1.1 FP7.

The IBM score is 4.3, with a network vector, low complexity, low privileges, no user interaction and a low integrity impact only. The record shows the same 4.3. The X-Force ID is 247621. There is no conflict on severity or versions.

The weakness is CWE-434, the same class as the sibling issue CVE-2023-25921. That one scores 8.5 because of a changed scope and high impacts. This one is limited to an integrity impact, which is why IBM rates it much lower. Do not read the low score as a reason to delay: the fix ships in the same release.

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

  1. List GKLM servers and confirm their versions.
  2. Upgrade to GKLM v4.2 or apply fix pack 4.1.1 FP7.
  3. Back up configuration and keys first.
  4. Limit console access to administrator networks.
  5. Close this ticket together with the four related CVEs in the same IBM bulletin.

Why it matters

Upload handling is a common source of weakness because the server must accept data it did not create. When it does not limit file types, an uploaded file can end up somewhere it is processed automatically. The low score for this CVE reflects a narrow impact in IBM's rating, not a different root cause.

Security teams often triage on score alone. In a shared bulletin like this one it makes more sense to treat all five CVEs as one upgrade task. The record does not flag the CVE in CISA KEV, and the IBM bulletin I read does not state exploitation.

Quick check

Why is this scored lower than CVE-2023-25921?

IBM rates this one with a low integrity impact only, and no changed scope. The 8.5 sibling has a changed scope and high impacts.

Is the fix the same?

Yes. IBM lists GKLM v4.2 and fix pack 4.1.1 FP7 for the whole set of CVEs in the bulletin.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.