CVE-2026-49501
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 9.5.0.0 through 9.10.1.7, and versions 9.11.0.0 through 9.13.0.2 contains an Improper Privilege Management 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 Improper Privilege Management vulnerability where a high-privileged attacker with local access can escalate privileges. This is a local privilege escalation flaw affecting versions 9.5.0.0-9.10.1.7 and 9.11.0.0-9.13.0.2.
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.5.0.0, < 9.10.1.8>= 9.11.0.0, < 9.13.1.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 installed PowerScale OneFS versionRun 'isi version' or 'isi status' from the CLI, or check System > Settings > General in the OneFS web UIAffected if The version falls within 9.5.0.0-9.10.1.7 or 9.11.0.0-9.13.0.2 (or is below 9.10.1.8 or 9.13.1.0)
You are affected if your PowerScale OneFS version is 9.5.0.0 through 9.10.1.7 or 9.11.0.0 through 9.13.0.2 and an attacker has local high-privileged access to the system.
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.89.13.1.0
Apply the vendor-supplied patch or upgrade to a fixed version of PowerScale OneFS beyond 9.10.1.7 or 9.13.0.2 as specified in Dell's security advisory.
9.13.1.0 or later (or 9.10.1.8+ if staying on 9.10.x branch)
- 1. Verify current PowerScale OneFS version by running 'isi version' or checking the web UI
- 2. Schedule a maintenance window as upgrades may require downtime
- 3. Backup critical data and configuration settings
- 4. Download the appropriate upgrade ISO from Dell Support (https://www.dell.com/support)
- 5. For systems on 9.5.0.0-9.10.1.7: Upgrade to 9.10.1.8 or later
- 6. For systems on 9.11.0.0-9.13.0.2: Upgrade to 9.13.1.0 or later (recommended)
- 7. Run the upgrade using 'isi upgrade' command or via the web UI under Cluster Management > Upgrade
- 8. Verify the upgrade completed successfully and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49501 — 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-49501 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