CVE-2026-21426
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 PowerScale OneFS, versions prior to 9.10.1.6 and versions 9.11.0.0 through 9.12.0.1, contains an execution with unnecessary privileges vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to denial of service, elevation of privileges, and 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 confidenceDell PowerScale OneFS contains a privilege escalation vulnerability where high-privileged local attackers can execute with unnecessary privileges, potentially achieving elevation of privileges beyond their assigned role, causing denial of service, and accessing sensitive information. The vulnerability affects versions prior to 9.10.1.6 and versions 9.11.0.0 through 9.12.0.1.
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< 9.10.1.6>= 9.11.0.0, < 9.13.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine OneFS version via CLIRun the command `isi version` or `isi system version` on the PowerScale node to retrieve the installed OneFS version numberAffected if The displayed version falls in the ranges < 9.10.1.6 OR >= 9.11.0.0 and < 9.13.0.0
-
Verify version via sysadminIf CLI access is unavailable, access the OneFS web admin interface and navigate to System > Settings > About to view the firmware versionAffected if The version shown is within the affected ranges listed above
-
Confirm version formatEnsure the version number follows the correct format (for example, 9.10.0.0, 9.11.0.0, 9.12.0.1) and compare numerically against the affected rangesAffected if A version like 9.10.1.5, 9.11.0.0 through 9.12.0.1, or any 9.12.x version is installed
-
Check for local administrative accountsReview local user accounts on the system using `isi auth users list` or through the Access > Users section in the web UI to identify any high-privileged local accountsAffected if High-privileged local accounts exist AND the OneFS version is in the affected ranges
You are affected if your PowerScale OneFS version is 9.10.1.5 or earlier, or between 9.11.0.0 and 9.12.0.1 (inclusive), or any 9.12.x version below 9.13.0.0.
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 · scoped9.10.1.69.13.0.0
Update Dell PowerScale OneFS to version 9.10.1.6 or later (or a version beyond 9.12.0.1) to remediate the vulnerability. Apply during a planned maintenance window following vendor upgrade procedures.
OneFS 9.13.0.0 or later (or 9.10.1.6 or later for the 9.10.x branch)
- 1. Verify current PowerScale OneFS version by running 'isi version' or checking the web administration console
- 2. Schedule a maintenance window for the upgrade (recommended to be during low-usage period)
- 3. Create a complete backup of the cluster configuration and verify backup integrity
- 4. Download the appropriate OneFS ISO image (version 9.13.0.0 or later) from Dell Support portal (support.dell.com)
- 5. Mount the ISO image and initiate upgrade using 'isi upgrade' command or through the web administration interface
- 6. Follow the on-screen prompts to complete the upgrade process
- 7. Verify the upgrade was successful by checking 'isi version' output shows 9.13.0.0 or later
- 8. Confirm all cluster services are operational and performing normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21426 — 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-21426 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