dbcve.org
Unisphere For PowermaxApplication · Dell

CVE-2026-26362

HIGH · 8.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 10.3.0.1 or later.
See remediation →
87/100
Remediation priority · High
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) a Relative Path Traversal vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to unauthorized modification of critical system 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 relative path traversal vulnerability that allows a low-privileged remote attacker to manipulate file paths in HTTP requests to access and modify system files outside the intended web root directory.

MitigationApply vendor-provided patches for PowerMax Unisphere 10.2; implement strict input validation on all file path parameters to reject sequences like '../' and ensure file access is restricted to allowed directories.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Unisphere for PowerMax version
    Access the Unisphere web interface or use the 'symcfg -version' command via service terminal to retrieve the installed software version. Compare the version number to the affected range (anything below 10.3.0.1).
    Affected if The installed version is 10.2.x or any version lower than 10.3.0.1
  2. Verify Unisphere web service is accessible
    Confirm the Unisphere web interface (typically HTTPS on port 8443 or 443) is reachable from the network. Check if the service is running using 'systemctl status unisphere' or equivalent service management command.
    Affected if The Unisphere web service is exposed and running on a network-accessible interface
  3. Review access logs for path traversal patterns
    Inspect Unisphere HTTP access logs (typically found in /var/log/unisphere/ or installation log directory) for requests containing '../' sequences, such as '../..', '../etc/passwd', or similar directory traversal patterns.
    Affected if Log entries contain URL-encoded or plain '../' sequences in request parameters, especially from low-privileged or unauthorized IP addresses
  4. Audit file system for unauthorized modifications
    Use file integrity monitoring tools or compare current file listings in system directories (/etc, /var, application data directories) against known baselines. Check for new or modified files outside the expected web root directory.
    Affected if Files exist or have been modified outside the intended Unisphere web root directory, or unexpected files appear in system directories

You are affected if Unisphere for PowerMax is running version 10.2.x (below 10.3.0.1), the web interface is network-accessible, and there are signs of path traversal exploitation in logs or file system.

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 vendor-provided patches for PowerMax Unisphere 10.2; implement strict input validation on all file path parameters to reject sequences like '../' and ensure file access is restricted to allowed directories.

Recommended fix High confidence

Unisphere for PowerMax version 10.3.0.1 or later

  1. Verify current Unisphere for PowerMax version by accessing the Unisphere interface or using the management CLI
  2. Review the Unisphere for PowerMax 10.3.0.1 release notes and upgrade prerequisites on Dell's support website
  3. Ensure all prerequisites are met including backup of current configuration
  4. Follow Dell's documented upgrade procedure for Unisphere for PowerMax, typically via the management interface or automated update mechanism
  5. After upgrade, verify the new version is 10.3.0.1 or later
  6. Validate that the path traversal vulnerability is resolved by confirming the system is running the patched version
Caveat Review Dell's release notes for version 10.3.0.1 for any compatibility or configuration changes that may affect your environment

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-26362 — 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-26362 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