Automated Threat Modeling

Brief Summary: Dell PowerStore SDNAS CVE 2026 111509, a Weak PRNG That Exposes NAS SSH and SFTP Sessions

A brief summary of CVE 2026 111509, a CVSS 9.1 cryptographically weak PRNG flaw (CWE 338) in Dell PowerStore SDNAS that could let a network attacker decrypt or tamper with NAS SSH and SFTP sessions. Covers the affected models and Dell's fixed PowerStoreT OS build.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-19

Brief Summary: Dell PowerStore SDNAS CVE 2026 111509, a Weak PRNG That Exposes NAS SSH and SFTP Sessions

Introduction

Dell PowerStore arrays that expose NAS shares over SSH and SFTP may have been protecting those sessions with random values that an attacker can predict. Dell scores the flaw, tracked as CVE 2026 111509, at CVSS 9.1 because a network attacker could decrypt or tamper with those sessions without credentials or any user interaction.

PowerStore is Dell Technologies' storage array family. SDNAS is its NAS component, and it handles the SSH and SFTP sessions affected here. Dell's storage portfolio spans primary storage, unstructured storage, and data protection, and Dell reports that storage net revenue grew 1% in fiscal 2026, driven mainly by core storage offerings. In its own blog, Dell cites IDC's Q1 2026 tracker as ranking it first in worldwide external enterprise storage with 31.2% share. Those figures give a sense of how widely Dell storage platforms are deployed in enterprise environments.

The reviewed sources do not include a public proof of concept, confirmed exploitation in the wild, or a named threat actor. We treat that as an information gap. It is not evidence that the issue is unexploited.

Technical information

Root cause

Dell, acting as the CNA, classifies the bug as CWE 338: Use of Cryptographically Weak Pseudo Random Number Generator. The published description is short: SDNAS used a cryptographically weak PRNG that could let a network attacker decrypt or tamper with NAS SSH and SFTP sessions.

SDNAS is proprietary, and Dell lists this issue under "Proprietary Code CVEs" in its advisory. There is no commit, diff, or source code to review, and the PowerStoreOS 5.1.0.0 release notes do not describe the fix. Dell has not disclosed which PRNG was used, how it was seeded, or exactly which protocol operation consumed its output.

Why the generator matters for SSH and SFTP

SSH (and SFTP, which runs over SSH) depends on unpredictable random values at several points:

  • The ephemeral Diffie Hellman or ECDH private values used during key exchange
  • The cookies and nonces exchanged in the handshake
  • The per-signature nonces when ECDSA or DSA host keys are used

If the generator behind these values is predictable or has little entropy, the security of the whole session collapses. Typical examples of this weakness class include a rand()-style generator that was never designed for cryptography, a seed derived from the current time or process ID, or a seed that is reused. An attacker who can narrow down the generator's output can recompute the ephemeral key exchange secret and, from it, the session keys.

Attack flow

Dell has not published an exploitation procedure. The sequence below describes how a CWE 338 weakness in an SSH implementation is generally abused, as outlined in the patch information we were given. It is not a confirmed description of Dell's internals.

  1. Observe the session. The attacker captures SSH or SFTP traffic to the SDNAS service, including the key exchange. The public record does not specify what network position is required.
  2. Predict the random values. Using weaknesses in the generator (for example a guessable seed), the attacker reconstructs or enumerates candidate values for the server's ephemeral key exchange private value.
  3. Recover the shared secret. With the ephemeral private value and the public values seen on the wire, the attacker computes the Diffie Hellman or ECDH shared secret.
  4. Derive session keys. From the shared secret, the attacker derives the session encryption and integrity keys.
  5. Read or forge traffic. With those keys, the attacker can decrypt the NAS SSH or SFTP session (confidentiality impact) or modify it in transit (integrity impact).

This model is consistent with Dell's scoring of High confidentiality and High integrity impact with no privileges required.

CVSS breakdown

The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N:

  • AV:N, AC:L: network reachable, low complexity
  • PR:N, UI:N: no privileges and no user interaction required
  • C:H, I:H: session contents can be read and altered
  • A:N: no availability impact is indicated

The scoring attributes do not establish that every network path to a device is exploitable, and they do not identify any session precondition. The CVE description and the advisory also do not describe any code execution or availability consequence for this CVE, and we do not infer one from the weakness category.

Patch information

Fixed release. Dell fixed CVE 2026 111509 in PowerStoreT OS 5.1.0.0 build 2798105. Advisory DSA 2026 479 lists that build as the minimum fixed version, and every earlier 5.1.x build is affected. The PowerStoreOS release matrix gives the build's release date as 29 October 2026. The advisory followed on 30 October 2026 (revision 1.0) and was revised on 17 November 2026 to add the 4.3.x LTS line.

What the fix likely involves. The standard remediation for CWE 338 is to draw all key material from a CSPRNG seeded by the operating system, such as getrandom(), /dev/urandom, or the crypto library's DRBG. Dell has not said whether that is exactly what it did.

The 4.3.x LTS line has no fix for this CVE yet. The 17 November 2026 revision added a 4.3.x row with build 4.3.1.3 build 2800620. That build fixes 11 of the CVEs in the advisory, and CVE 2026 111509 is not one of them. Dell says LTS fixes "are expected to be released in batches across multiple patches, starting in November 2026." For now, the only fixed code for this CVE is the 5.1.0.0 line.

Upgrade path. According to Dell's upgrade path table:

  • PowerStore T and Q systems on any 4.x release can upgrade directly to 5.x.
  • Systems on 3.x must go through 4.x first (3.x → 4.x → 5.x).
  • Review the matrix notes before upgrading, such as the LACP bond0 note for 4.4.x and 5.0.x and the STIG note.

The same 5.1.0.0 build also fixes more than 40 other CVEs from DSA 2026 479, including several critical SDNAS bugs.

Existing keys may still be weak. Upgrading changes how new random values are generated. It cannot repair keys that the weak generator already produced. If SDNAS generated its SSH host keys or other long-lived keys while the flaw was present, those keys may remain predictable after the upgrade. The advisory says nothing about key rotation, so we recommend asking Dell support whether the upgrade regenerates the NAS SSH host keys.

Affected systems and versions

The CVE record and NVD's affected products data (sourced from Dell) show the same cutoff for all 15 models: releases before PowerStoreT OS 5.1.0.0 build 2798105 are affected, and that build or later is fixed.

  • PowerStore T models: 500T, 1000T, 1200T, 3000T, 3200T, 5000T, 5200T, 7000T, 9000T, 9200T
  • PowerStore Q models: 3200Q, 5200Q
  • Other listed models: 1500, 5500, 9500

For the 4.3.x LTS line, the advisory names PowerStore 500T, 1000T, 1200T, 3000T, 3200Q, 3200T, 5000T, 5200Q, 5200T, 7000T, 9000T, and 9200T. As noted above, the current LTS build 4.3.1.3 build 2800620 does not address this CVE.

The affected configuration is any of these systems running a vulnerable release with SDNAS handling NAS SSH or SFTP sessions.

Vendor security history

Dell's Product Security Incident Response Team coordinates the response to and disclosure of product vulnerabilities, and Dell's policy states that advisories are published after analysis and identification of solutions. DSA 2026 479 is a large bundled advisory: the 5.1.0.0 build addresses more than 40 CVEs, several of them critical SDNAS issues. The sources we reviewed do not support a broader rating of Dell's security track record or a comparison with other storage vendors.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization