Vulnerabilities
Dell PowerStore: a low-privilege account becomes root
Dell's DSA-2026-479 update fixes 44 PowerStore flaws, including command injection that gives a limited user root on the array. What to patch and how to isolate the management plane.
Dell has published a large security update for PowerStore, its enterprise storage platform, that fixes 44 separate vulnerabilities on the appliance. Seven of them carry a Common Vulnerability Scoring System (CVSS) base score of 9.8 out of 10, and several more let an attacker who already holds a low-privilege account run commands as root on the array. The advisory is DSA-2026-479, dated October 30, 2026, and the only fix Dell lists is an upgrade to PowerStore OS version 5.1.0.0-2798105 or later.
A storage array does not face the internet, so the instinct is to treat this as a slow-lane patch. That instinct is wrong here. PowerStore holds the data behind the business: virtual machine images, databases, file shares and backups. The flaws that matter most need only a foothold on the management network, and they turn that foothold into root on the appliance or administrator in the management interface. Dell reports no exploitation so far, which makes this the right week to move, before a working exploit is published.
How these flaws work
The headline problem is operating-system command injection. The clearest example is CVE-2026-103813, scored 9.1. An authenticated user with limited privileges supplies input that the appliance software hands to a shell without separating the data from the command. The attacker's text is run as a command, and because the PowerStore process runs as root, so does the attacker's input. A normal, low-rights account becomes full root on the appliance. Two more command-injection flaws, CVE-2026-116448 and CVE-2026-116449, both rated 9.8, do the same inside the software-defined network-attached storage (SDNAS) file-services component and give root on the storage node to an attacker who can reach it from the internal network.
CVE-2026-111545, scored 8.8, is a SQL injection. The management interface builds a database query out of user input without keeping the input and the query apart, so an authenticated attacker can read rows they were never meant to see and change others. Dell says this one discloses stored private keys and lets an attacker tamper with the trusted certificates the array relies on. A private key in the wrong hands means someone can impersonate the array or decrypt the sessions it protects, so this flaw outlives the patch if the key was taken first.
CVE-2026-116411, also 8.8, is a server-side request forgery (SSRF): a feature meant to make the appliance fetch a resource can be pointed at internal addresses instead, so a limited user reads responses from systems they cannot reach directly. CVE-2026-86356, 8.8, is an authorization bypass that elevates an ordinary user to administrator, because a request that should be refused is accepted. Two integer-overflow bugs round out the high-severity set: CVE-2026-107524 (8.8) and CVE-2026-107523 (8.7). In both, arithmetic on a size or offset wraps past its maximum and becomes a small or negative value, so a bounds check that should reject the operation passes. The result is out-of-bounds data access, corruption of volume data, or denial of service.
Why a storage array is worth this effort
No exploitation has been reported, so the useful question is what an attacker would gain from chaining these, and why that is worse on storage than on a typical server. An array is where everything ends up. Root on the appliance, or administrator in its management plane, is read and write access to every volume, snapshot and replication copy it serves, including the backups a recovery plan depends on. An attacker in that position can copy data out quietly, plant persistence that survives a host rebuild, or destroy the snapshots that would otherwise let you roll back a ransomware event.
The access requirement is the part that catches teams out. Several of these flaws are "authenticated" and "low privilege," which reads as reassuring until you count how many accounts can reach a storage management interface on a flat internal network: monitoring tools, backup software, directory-integrated operators, old service accounts nobody owns. Any one of those, or any attacker who has already phished a single internal credential, is the low-privilege foothold CVE-2026-103813 needs. The management plane is treated as trusted precisely because it is internal, and that is the assumption these bugs break.
What to do
- Upgrade every PowerStore appliance to PowerStore OS 5.1.0.0-2798105 or later. Dell lists no workaround and no per-flaw mitigation; the upgrade is the only fix, and it closes all 44 issues at once. Include any secondary or test appliances, not just production.
- If you cannot schedule the upgrade immediately, shrink the attack surface by isolating the management interface. Put it on an administration-only network segment or VLAN, and allow management and SDNAS traffic only from known admin jump hosts and the specific backup and monitoring systems that need it. Almost every serious flaw in this batch needs reachability to the management plane or the internal storage network, so cutting that reachability buys time.
- Review who holds any account on the array. List every local account, every service account, and every identity brought in through directory integration, and remove the ones that are stale or unexplained. Because a limited account is enough to reach root here, the account list is part of the exposure, not a separate housekeeping task.
- If an appliance was reachable by untrusted users before you patched, assume the SQL-injection key disclosure (CVE-2026-111545) may have fired. Rotate the private keys and replace the certificates the array stored, and review administrative activity and audit logs for actions you cannot account for. Rotating keys after the patch does nothing for a key that was already copied.
The recurring lesson is that "internal only" is not a security boundary on its own. A management interface that every tool and operator can reach is one credential away from being an attacker's interface too. Segmenting the storage and management network, and keeping the account list on it short, is what turns a low-privilege flaw into a non-event.
Isolating and testing a management plane like this is the kind of work we do in a network penetration test, and locking down the appliance's configuration and account list is the heart of safeguarding and hardening. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.
Sources: Dell DSA-2026-479, NVD CVE-2026-103813, NVD CVE-2026-111545, NVD CVE-2026-116411, NVD CVE-2026-86356, NVD CVE-2026-107524, NVD CVE-2026-107523, Daily Security Review on DSA-2026-479. </content> </invoke>