dbcve.org
Powerscale OnefsApplication · Dell

CVE-2026-22280

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 9.5.1.6 / 9.7.1.11 or later.
See remediation →
57/100
Remediation priority · Elevated
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 PowerScale OneFS, versions 9.5.0.0 through 9.5.1.5, versions 9.6.0.0 through 9.7.1.10, versions 9.8.0.0 through 9.10.1.3, versions starting from 9.11.0.0 and prior to 9.13.0.0, contains an incorrect permission assignment for critical resource vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to denial of service.

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 PowerScale OneFS versions prior to 9.13.0.0 contain an incorrect permission assignment vulnerability where low-privileged local users can access critical system resources, potentially leading to denial of service.

MitigationUpgrade to Dell PowerScale OneFS version 9.13.0.0 or later which addresses the permission assignment issue.

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
Powerscale OnefsApplication
Affected:>= 9.5.0.0, < 9.5.1.6>= 9.6.0.0, < 9.7.1.11>= 9.8.0.0, < 9.10.1.4>= 9.11.0.0, < 9.13.0.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify installed OneFS version
    Run the command 'isi version' or 'isi status' on the PowerScale CLI to retrieve the current OneFS version number
    Affected if The displayed version falls within any of these ranges: 9.5.0.0-9.5.1.5, 9.6.0.0-9.7.1.10, 9.8.0.0-9.10.1.3, or 9.11.0.0-9.12.x.x (any patch level below 9.13.0.0)
  2. Verify version is within affected range
    Compare the installed version number to the affected ranges: versions 9.5.x below 9.5.1.6, 9.6.x and 9.7.x below 9.7.1.11, 9.8.x through 9.10.x below 9.10.1.4, and 9.11.x through 9.12.x below 9.13.0.0
    Affected if The version is lower than 9.13.0.0 and matches one of the specific vulnerable version ranges listed in the CVE
  3. Confirm local user access exists
    Check if local low-privileged user accounts exist on the system using 'isi auth users list' or by reviewing /var/account/pacct if accessible
    Affected if Local non-admin user accounts are present on the system (this condition combined with a vulnerable version means the flaw can be exploited)
  4. Check for critical resource access
    Review system configuration for any custom permission settings on critical directories such as /ifs or system config areas that may be improperly exposed
    Affected if Critical system resources have permissions that allow access by non-privileged local users beyond intended boundaries

The environment is affected if PowerScale OneFS is running a version lower than 9.13.0.0 and falls within any of the four vulnerable version ranges, and local low-privileged user accounts exist on the system.

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 9.5.1.6 / 9.7.1.11 / 9.10.1.4 or later
Fixed in 9.5.1.69.7.1.119.10.1.4
Interim mitigation

Upgrade to Dell PowerScale OneFS version 9.13.0.0 or later which addresses the permission assignment issue.

Recommended fix High confidence

9.13.0.0 (or branch-specific: 9.5.1.6 for 9.5.x, 9.7.1.11 for 9.6-9.7.x, 9.10.1.4 for 9.8-9.10.x)

  1. Review current PowerScale OneFS version using 'isi version' or through the web管理界面
  2. Identify the appropriate upgrade path based on current version branch (9.5.x, 9.6-9.7.x, 9.8-9.10.x, or 9.11.x+)
  3. Download the corresponding Dell PowerScale OneFS iso/image from Dell support portal (support.dell.com)
  4. Follow Dell PowerScale upgrade documentation to create a backup and perform pre-upgrade checks
  5. Execute the upgrade process using 'isi upgrade' command or through the web管理界面
  6. Verify successful upgrade by checking the new version with 'isi version'
  7. Confirm all services are running normally post-upgrade
Caveat Review Dell upgrade guide for any configuration changes or migration steps required for your version branch; test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-22280 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