Unisphere For PowermaxApplication · Dell

CVE-2026-54468

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 10.3.0.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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
Dell Unisphere for PowerMax, version(s) 10.3.0.5 and prior, contain(s) a path traversal vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability to read arbitrary files.

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 · high confidence

Dell Unisphere for PowerMax versions 10.3.0.5 and prior contain a path traversal vulnerability that allows a low-privileged attacker with remote access to read arbitrary files on the system by manipulating file path inputs with traversal sequences (e.g., ../). This is a classic directory traversal issue stemming from insufficient input validation.

MitigationApply the vendor patch when released by Dell. In the interim, restrict network access to Unisphere management interfaces to authorized personnel only and monitor for suspicious path traversal patterns in request logs.

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
Unisphere For PowermaxApplication
Affected:< 10.3.0.7

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine Unisphere for PowerMax version
    Log into the Unisphere web interface and navigate to the About or System Information page. Alternatively, access the system via SSH and use the 'unisphere -version' command or check the installation directory for version metadata files.
    Affected if The installed version is 10.3.0.5 or prior, or any version lower than 10.3.0.7
  2. Verify remote management interface exposure
    Check network configuration to determine if the Unisphere management ports (typically HTTPS port 8443 or 443) are exposed to network segments beyond the trusted administrative zone. Review firewall rules and access control lists protecting the Unisphere server.
    Affected if The Unisphere management interface is accessible from networks outside the trusted administrative zone
  3. Inspect request logs for path traversal patterns
    Review Unisphere access logs and web server logs for patterns containing '../' sequences, encoded traversal sequences (e.g., %2e%2e%2f), or unusual file path requests targeting system directories such as /etc/, /windows/, or C:\.
    Affected if Log analysis reveals path traversal attempts in request history, indicating active exploitation attempts or successful attacks

You are affected if Unisphere for PowerMax version is below 10.3.0.7 AND the management interface is reachable from an untrusted network.

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 10.3.0.7 or later
Fixed in 10.3.0.7
Interim mitigation

Apply the vendor patch when released by Dell. In the interim, restrict network access to Unisphere management interfaces to authorized personnel only and monitor for suspicious path traversal patterns in request logs.

Recommended fix Moderate confidence

10.3.0.7

  1. Obtain Unisphere for PowerMax version 10.3.0.7 or later from Dell's official support website
  2. Review the Dell Unisphere for PowerMax upgrade guide and release notes before initiating the update
  3. Follow Dell's documented upgrade procedure for Unisphere for PowerMax, ensuring proper backups are in place
  4. After completing the upgrade, verify the installation was successful
  5. Confirm that the path traversal vulnerability is no longer present by testing file access restrictions

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

Fix this in Unisphere For Powermax Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2026-54468 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