Unisphere For PowermaxApplication · Dell

CVE-2026-26358

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) a Missing Authorization vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Unauthorized access.

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 missing authorization vulnerability that allows a low-privileged remote attacker to bypass access controls and gain unauthorized access to functionality or data within the storage management interface.

MitigationApply the vendor-provided patch or hotfix for CVE-2026-26358 when released. In the interim, implement network segmentation to restrict access to Unisphere management interfaces to only authorized administration networks, and review user role assignments to ensure least privilege.

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. Confirm Dell Unisphere for PowerMax is deployed
    Identify whether Dell Unisphere for PowerMax storage management software is installed in your environment. This is typically deployed as a virtual appliance or on dedicated hardware for managing PowerMax storage arrays.
    Affected if The product is present in your environment and has not been upgraded to version 10.3.0.1 or later.
  2. Identify the installed version
    Access the Unisphere management interface and navigate to the About or System Information section to view the installed version number. Alternatively, check the system documentation or use the Unisphere CLI 'about' command if available.
    Affected if The displayed version is earlier than 10.3.0.1 (for example, 10.2.x, 10.1.x, or earlier).
  3. Compare version against affected range
    Document the exact version number found and compare it against the affected range: any version less than 10.3.0.1 is vulnerable.
    Affected if The installed version falls below 10.3.0.1 (for example, 10.2.0.0, 10.2.0.1, 10.1.0.0).
  4. Assess network accessibility
    Determine whether the Unisphere management interface is accessible from network segments outside of the dedicated administration network. Check firewall rules, exposed interfaces, and access paths.
    Affected if The Unisphere interface is network-accessible to untrusted users or segments, as this enables the low-privileged remote attacker to attempt the authorization bypass.

You are affected if Dell Unisphere for PowerMax is running version 10.3.0.0 or earlier and the management interface is network-accessible to the attacker.

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-provided patch or hotfix for CVE-2026-26358 when released. In the interim, implement network segmentation to restrict access to Unisphere management interfaces to only authorized administration networks, and review user role assignments to ensure least privilege.

Recommended fix High confidence

10.3.0.1

  1. Upgrade Dell Unisphere for PowerMax to version 10.3.0.1 or later
Caveat Review Dell Unisphere for PowerMax 10.3.0.1 release notes for any compatibility or configuration changes before upgrading

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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