dbcve.org
Storage ScaleApplication · Ibm

CVE-2025-14604

HIGH · 7.8 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 5.2.3.6 / 6.0.0.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Storage Scale IBM S through rage Scale 5.2.3.0 - 5.2.3.5, and IBM S through rage Scale 6.0.0.0 - 6.0.0.1 could allow a local user to unintentionally trigger additional permissions for resources in a way that allows that resource to be executed by unintended actors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Storage Scale versions 5.2.3.0-5.2.3.5 and 6.0.0.0-6.0.0.1 contain a local permission escalation vulnerability where a local user can unintentionally trigger additional permissions for resources, allowing those resources to be executed by unintended actors. This is a local privilege escalation issue affecting resource access controls.

MitigationReview and restrict file/system resource permissions in IBM Storage Scale to ensure resources cannot be accessed by unintended local users. Apply any IBM-provided patches for this vulnerability or upgrade to a fixed version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Storage ScaleApplication
Affected:>= 5.2.3.0, < 5.2.3.6>= 6.0.0.0, < 6.0.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Storage Scale version
    Run 'mmfsadm dump version' or check /usr/lpp/iversion file on the storage scale nodes
    Affected if Version falls within 5.2.3.0-5.2.3.5 or 6.0.0.0-6.0.0.1 ranges
  2. Verify exact version number
    Run 'lsitv' or check GPFS version via 'mmlsconfig' output
    Affected if Version is lower than 5.2.3.6 or 6.0.0.2
  3. Inspect resource permission settings
    Run 'mmfsadm dump permissions' or examine file permissions on /var/mmfs and /usr/lpp/iversion directories
    Affected if Resources show permissions allowing access by unintended local users
  4. Check for unauthorized resource access
    Review audit logs in /var/mmfs/audit/ for resource access patterns by non-privileged users
    Affected if Non-privileged local users have executed resources they should not have access to
  5. Review user and group mappings
    Run 'mmuserauth' or check /var/mmfs/etc/ui_group mappings for improper privilege assignments
    Affected if Local users have been granted elevated access to resources unexpectedly

A system is affected if it runs IBM Storage Scale versions 5.2.3.0 through 5.2.3.5 or 6.0.0.0 through 6.0.0.1, and exhibits unauthorized resource access by local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.3.6 / 6.0.0.2 or later
Fixed in 5.2.3.66.0.0.2
Interim mitigation

Review and restrict file/system resource permissions in IBM Storage Scale to ensure resources cannot be accessed by unintended local users. Apply any IBM-provided patches for this vulnerability or upgrade to a fixed version if available.

Recommended fix Moderate confidence

IBM Storage Scale 5.2.3.6 or later for the 5.2.x line; IBM Storage Scale 6.0.0.2 or later for the 6.0.x line

  1. Identify the currently installed IBM Storage Scale version using 'mmdsh' or the scale версия command
  2. For IBM Storage Scale 5.2.x: Plan upgrade to version 5.2.3.6 or later
  3. For IBM Storage Scale 6.0.x: Plan upgrade to version 6.0.0.2 or later
  4. Review IBM Storage Scale upgrade documentation for your specific version path
  5. Schedule maintenance window as upgrades may require cluster downtime
  6. Back up all critical data and cluster configuration before proceeding
  7. Execute upgrade following IBM-provided procedures (typically using 'mmupgrader' or GUI-based upgrade)
  8. Verify the installed version post-upgrade matches the target fixed version
Caveat IBM Storage Scale minor version upgrades may introduce compatibility changes with client applications and protocols; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storage Scale Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14604 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data