dbcve.org
Powerscale OnefsApplication · Dell

CVE-2026-22278

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 9.13.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 prior to 9.13.0.0 contains an improper restriction of excessive authentication attempts vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Unauthorized access.

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 confidence

Dell PowerScale OneFS versions prior to 9.13.0.0 fail to properly restrict excessive authentication attempts, allowing unauthenticated remote attackers to perform unlimited login attempts (brute force/password spray) without account lockout or rate limiting, potentially leading to unauthorized access to the system.

MitigationUpgrade Dell PowerScale OneFS to version 9.13.0.0 or later to obtain the patch that implements proper authentication attempt restrictions.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PowerScale OneFS version
    Run the OneFS CLI command to display the current firmware version (commonly 'isi version' or check through the web administration interface under System > Overview)
    Affected if The displayed version is any release prior to 9.13.0.0 (for example 9.12.x, 9.11.x, earlier releases)
  2. Verify account lockout policy configuration
    Access the OneFS authentication settings through the web UI (Platform API or isi command line) and examine the account lockout parameters that control how many failed attempts trigger a lockout
    Affected if No account lockout policy is defined, or the lockout threshold is set to zero (unlimited attempts allowed) or is missing entirely
  3. Confirm authentication rate limiting is enabled
    Review the authentication rate limiting or throttling configuration in OneFS settings (typically found under Security > Authentication or via the isi auth settings CLI)
    Affected if Rate limiting is disabled, not configured, or set to allow unlimited authentication attempts per time window
  4. Inspect authentication logs for brute force activity
    Examine OneFS audit or authentication logs (via 'isi audit' or the logs directory) for evidence of repeated failed login attempts from the same source without triggering any blocks
    Affected if Logs show many failed authentication attempts from a single source without any account lockout or rate limit intervention occurring

Your environment is affected if the installed OneFS version is below 9.13.0.0 AND no account lockout or rate limiting controls are actively enforced in the authentication configuration.

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.13.0.0 or later
Fixed in 9.13.0.0
Interim mitigation

Upgrade Dell PowerScale OneFS to version 9.13.0.0 or later to obtain the patch that implements proper authentication attempt restrictions.

Recommended fix High confidence

OneFS 9.13.0.0

  1. Back up the current OneFS configuration and critical data before proceeding with the upgrade
  2. Download the OneFS 9.13.0.0 update package from Dell Technologies support website
  3. Access the PowerScale OneFS web administration interface or use the CLI (isi升级) to initiate the upgrade
  4. Follow the on-screen prompts or use the 'isi升级 -a' command to apply the OneFS 9.13.0.0 update
  5. Allow the system to complete the upgrade process and automatically reboot as needed
  6. After the system restarts, verify the OneFS version is 9.13.0.0 or later using 'isi version' or the web UI
  7. Confirm the authentication mechanism is functioning correctly and the vulnerability is remediated
Caveat Standard OneFS upgrade best practices apply; ensure compatibility with existing integrations and test 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
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22278 — 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-22278 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