dbcve.org
Unisphere For PowermaxApplication · Dell

CVE-2026-26361

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 10.3.0.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Information disclosure.

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 (External Control of File Name or Path) vulnerability. A low-privileged remote attacker can manipulate file path inputs to access sensitive files outside the intended directory, resulting in information disclosure. The medium CVSS score reflects limited impact due to requiring authentication.

MitigationImplement strict input validation and canonicalization for all file path parameters to prevent directory traversal sequences (../). Restrict file access permissions and add web application firewall rules to detect and block path traversal attempts.

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
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. Confirm Dell Unisphere for PowerMax is installed
    Check for the Unisphere web application by accessing the host on typical ports (8443, 443) or locate installation directories. On Windows, check C:\Program Files\Dell\Unisphere or similar. On Linux, check /opt/dell/unisphere or /usr/local/unisphere.
    Affected if Unisphere web interface is accessible or installation directory exists on the system
  2. Identify installed version
    Log into the Unisphere web interface and navigate to Support > About, or check the version file in the installation directory. Alternatively, check the version via API endpoint /api/unisphere/version or in the application logs.
    Affected if Installed version is lower than 10.3.0.1 (e.g., 10.2.x, 10.1.x, etc.)
  3. Verify web interface is accessible
    Attempt to reach the Unisphere login page via HTTPS on port 8443 or 443. Confirm the application responds and presents a login prompt.
    Affected if Unisphere web interface is reachable over the network without being blocked by firewall
  4. Confirm authentication is in use
    Check that the login page requires credentials. Verify that low-privileged user accounts can be created or exist in the system via User Management settings.
    Affected if Low-privileged remote authentication is available and the web application accepts file path parameters without additional validation
  5. Test for path traversal accessibility
    If authorized in a non-production environment, inspect form fields or URL parameters that accept file names or paths. Look for parameters that could accept directory traversal sequences like ../../etc/passwd.
    Affected if The application accepts file path inputs that are not strictly validated, allowing traversal sequences to access files outside the intended web root directory

You are affected if Dell Unisphere for PowerMax is running with a version lower than 10.3.0.1 and its web interface is accessible to remote users, allowing file path inputs to be manipulated without proper validation.

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

Implement strict input validation and canonicalization for all file path parameters to prevent directory traversal sequences (../). Restrict file access permissions and add web application firewall rules to detect and block path traversal attempts.

Recommended fix High confidence

10.3.0.1 or later

  1. 1. Back up current Unisphere for PowerMax configuration and any critical data
  2. 2. Download Unisphere for PowerMax version 10.3.0.1 (or latest available) from Dell Support website (support.dell.com)
  3. 3. Follow Dell's documented upgrade procedure for Unisphere for PowerMax - typically involves stopping services, running the installer, and validating the installation
  4. 4. After upgrade, verify the Unisphere version shows 10.3.0.1 or later in the About/Version information
  5. 5. Confirm normal operations resume and the vulnerability is no longer present

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