How to Fix CVE-2026-22270: PowerScale OneFS, (Bundle Sibling)
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-22270 is a sibling vulnerability in the same vendor advisory as CVE-2026-21421. Apply the same patched build and you close both. The technical detail below is what differs.
| Severity | 6.7 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | PowerScale OneFS, 9.11.0.0 through 9.12.0.1 to <9.13.0.0 or later; PowerScale OneFS, prior to 9.10.1.6 to <9.10.1.6 or later |
| Fixed in | Same patched build as CVE-2026-21421 |
| Type (CWE) | CWE-427: Uncontrolled Search Path Element |
What's different about CVE-2026-22270?
Dell PowerScale OneFS, versions prior to 9.10.1.6 and versions 9.11.0.0 through 9.12.0.1, contains an uncontrolled search path element vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to denial of service, elevation of privileges, and information disclosure.
How to fix CVE-2026-22270
Apply the patched build per the primary write-up: How to Fix CVE-2026-21421. All commands, verification steps, and rollback notes for PowerScale OneFS, are listed there.
Frequently asked questions
Does the CVE-2026-21421 patch close CVE-2026-22270?
Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.
Is CVE-2026-22270 listed in CISA KEV?
No public KEV listing at the time of this writing.
Where is the official advisory?
See https://www.dell.com/support/kbdoc/en-sg/000432452/dsa-2026-038-security-update-for-dell-powerscale-onefs-multiple-vulnerabilities
References
- Official vendor advisory: https://www.dell.com/support/kbdoc/en-sg/000432452/dsa-2026-038-security-update-for-dell-powerscale-onefs-multiple-vulnerabilities
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22270
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary: How to Fix CVE-2026-21421
*Written by Sai Kiran Pandrala. Part of the PowerScale OneFS, bundle. Full procedure at how-to-fix-cve-2026-21421.*