CVE-2026-26360
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 · uneditedDell 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 to delete 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 confidenceDell Unisphere for PowerMax version 10.2 contains a path traversal vulnerability (CWE-22) allowing a low-privileged remote attacker to delete arbitrary files on the system by manipulating file paths in delete 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< 10.3.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Dell Unisphere for PowerMax is installedLocate the Unisphere installation directory or check installed software packages for 'Unisphere for PowerMax' or 'Unisphere'Affected if Dell Unisphere for PowerMax is present on the system
-
Check the installed version numberAccess the Unisphere admin interface and navigate to About or Support page to view the version, or run the appropriate version command for the installationAffected if The version is below 10.3.0.1 (e.g., 10.2.x, 10.1.x, etc.)
-
Verify web interface is accessibleConfirm the Unisphere web application is reachable via HTTP/HTTPS on the configured port (typically 8443 or 443)Affected if The web interface is exposed and the version is below 10.3.0.1
-
Check file operation permissionsReview the configuration and permissions on the file system directories that Unisphere uses for uploads and file operationsAffected if Low-privileged users can trigger file deletion operations and the version is below 10.3.0.1
If Dell Unisphere for PowerMax is installed with a version lower than 10.3.0.1 and the web interface is accessible, the environment is potentially affected by this path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.3.0.1
Apply vendor-supplied patch for CVE-2026-26360. If no patch available, implement strict input validation on file path parameters, use allow-lists for permitted deletion paths, and ensure file deletion operations run with minimal privileges.
Unisphere for PowerMax 10.3.0.1
- Download Unisphere for PowerMax version 10.3.0.1 or later from Dell's support website
- Review the Unisphere for PowerMax upgrade guide for your environment
- Execute the upgrade following Dell's documented upgrade procedure
- Verify the upgrade was successful by checking the version number in Unisphere
- Confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26360 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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