dbcve.org
Unisphere For PowermaxApplication · Dell

CVE-2026-26359

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 10.3.0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Dell Unisphere for PowerMax, version(s) 10.2, contain(s) an External Control of File Name or Path vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to the ability to overwrite 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 · moderate confidence

Dell Unisphere for PowerMax version 10.2 contains a path traversal vulnerability (CWE-22) that allows a low-privileged remote attacker to overwrite arbitrary files on the system by manipulating file paths in user-controlled inputs. This could lead to configuration tampering, code execution escalation, or denial of service.

MitigationApply the vendor-supplied patch for CVE-2026-26359. If unavailable, restrict network access to Unisphere management interfaces and monitor for suspicious file write operations.

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.1

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
High
Availability
High

CVSS:3.1/AV:N/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 the installed Unisphere for PowerMax version
    Access the Unisphere management interface and navigate to the About or System Information section, or use the command line interface if available to retrieve the software version
    Affected if The installed version is 10.2.x or any version below 10.3.0.1
  2. Confirm Unisphere management interface is network-accessible
    Verify network connectivity to the Unisphere management port (typically port 443/HTTPS) from external networks or non-management VLANs
    Affected if The management interface is exposed to untrusted networks or the internet
  3. Review system logs for path traversal indicators
    Examine Unisphere and system audit logs for failed or suspicious file access attempts, especially those containing patterns like ../ or ..\ in request parameters
    Affected if Logs show any file path manipulation attempts or unauthorized file write operations
  4. Inspect file system for unexpected modifications
    Check configuration files, scripts, or executables in the Unisphere installation directory for unexpected changes or new files that were not part of the original installation
    Affected if Unexpected files or modifications exist in the Unisphere installation or configuration directories

A user is affected if their Dell Unisphere for PowerMax installation is version 10.2.x or any version below 10.3.0.1 and the management interface is network-accessible to untrusted 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 10.3.0.1 or later
Fixed in 10.3.0.1
Interim mitigation

Apply the vendor-supplied patch for CVE-2026-26359. If unavailable, restrict network access to Unisphere management interfaces and monitor for suspicious file write operations.

Recommended fix Moderate confidence

10.3.0.1

  1. Review the current Unisphere for PowerMax version by accessing the Unisphere UI or checking system documentation
  2. Schedule a maintenance window for the upgrade following Dell's recommended upgrade procedures
  3. Download Unisphere for PowerMax version 10.3.0.1 or later from the Dell Support website (support.dell.com)
  4. Follow Dell's documented upgrade procedure for Unisphere for PowerMax, which typically includes: backing up the current configuration, stopping services, applying the upgrade, verifying the installation, and restarting services
  5. After upgrade, verify that the Unisphere for PowerMax version is 10.3.0.1 or later using the UI or CLI
  6. Confirm the vulnerability is remediated by reviewing the security release notes for the new version
Caveat Review Dell's release notes for 10.3.0.1 to check for any configuration or feature changes that may require adjustment; enterprise upgrades should be tested in a staging environment first

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

Fix this in Unisphere For Powermax Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26359 — 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-2026-26359 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