CVE-2026-21424
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 Elevation of privileges.
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 an execution with unnecessary privileges vulnerability where the application runs with more privileges than required. A high-privileged attacker with local system access can exploit this to gain elevated privileges beyond their current permissions.
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.
-
Confirm PowerScale OneFS is runningIdentify whether the system is a Dell PowerScale storage array running OneFS. This is typically visible in the system hostname, admin web UI, or system documentation.Affected if System is not a Dell PowerScale OneFS array (not applicable)
-
Determine installed OneFS versionRun the OneFS CLI command to retrieve the version, such as `isi version` or `isi -v`. Alternatively, access the OneFS web administration interface and navigate to the About or System Information page.Affected if Unable to retrieve the OneFS version number
-
Compare version against affected rangesExamine the retrieved version number. Affected versions are: any version below 9.10.1.6, or any version from 9.11.0.0 up to but not including 9.13.0.0. Safe versions are 9.10.1.6 through 9.10.x.x, 9.12.1.0 and later, or 9.13.0.0 and later.Affected if Installed version is before 9.10.1.6, or between 9.11.0.0 and 9.12.0.x, or between 9.12.1.0 and 9.12.x.x but before 9.13.0.0
You are affected if your PowerScale OneFS version is earlier than 9.10.1.6, or falls in the 9.11.x or 9.12.x release lines before 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
Apply the vendor-supplied patch by upgrading to Dell PowerScale OneFS version 9.10.1.6 or later, or version 9.12.1.0 or later.
OneFS 9.13.0.0 (or 9.10.1.6 for older 9.10.x installations)
- 1. Back up all critical data and OneFS configuration using the 'isi backup' command or web UI
- 2. Download the OneFS 9.13.0.0 upgrade package from Dell Support website (www.dell.com/support)
- 3. Access the OneFS web UI or CLI (via SSH) with administrative credentials
- 4. In web UI: Navigate to Cluster Management > Software Update > Upload and install the upgrade package
- 5. Alternatively via CLI: Run 'isi upgrade' commands to stage and apply the upgrade
- 6. After upgrade completes, verify the version by running 'isi version' or checking the web UI
- 7. Confirm the vulnerability is resolved by verifying the OneFS version shows 9.13.0.0 or 9.10.1.6
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-21424 — 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-21424 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