Cyber Resilience

CVE-2026-22280

LPE in Dell Powerscale Onefs 9.5.0.0 – 9.5.1.6

Published
22 January 2026
Modified
28 January 2026
Patch / advisory
CVSS Score v3.1 5.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0012 2th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-22280 is a medium-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Dell Powerscale Onefs. Its CVSS base score is 5.0 (Medium).

Operationally, ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

potentially exploit this vulnerability, leading to denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-47475Same product: Dell Powerscale Onefs
CVE-2026-25907Same product: Dell Powerscale Onefs
CVE-2024-25961Same product: Dell Powerscale Onefs
CVE-2026-22281Same product: Dell Powerscale Onefs
CVE-2023-32494Same product: Dell Powerscale Onefs
CVE-2025-27690Same product: Dell Powerscale Onefs
CVE-2023-32495Same product: Dell Powerscale Onefs
CVE-2026-49501Same product: Dell Powerscale Onefs
CVE-2024-25954Same product: Dell Powerscale Onefs
CVE-2025-30101Same product: Dell Powerscale Onefs

Affected Assets

dell
powerscale onefs
9.5.0.0 — 9.5.1.6 · 9.6.0.0 — 9.7.1.11 · 9.8.0.0 — 9.10.1.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • CM-5 Access Restrictions for Change
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces correct access permissions on critical OneFS resources so that low-privileged local accounts cannot trigger denial of service.

prevent

Ensures low-privileged local users receive only the minimum rights required, eliminating the ability to misuse incorrectly assigned permissions on critical resources.

prevent

Restricts which accounts may modify permissions or critical resource settings, reducing the chance that flawed assignments reach production OneFS clusters.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires defining, enforcing, and reviewing access permissions and least privilege on resources.

PR.PS-01 mostly match
prevents

Hardened baselines and configuration management explicitly include correct permission settings for critical resources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.

prevents

Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.

prevents

Documented authorization, expiry rules, and audit logging of privileged accounts make it harder for critical resources to retain overly permissive or stale permission assignments.

prevents

Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.

prevents

Enforcing differentiated permissions on the source-code repository and program listings stops the assignment of overly broad default or inherited permissions to critical resources.

prevents

By defining and enforcing secure permission settings in configuration templates, the control reduces the likelihood that critical resources receive incorrect permission assignments.

References