VulnerabilityPublished 27 Jun 2025Updated 26 Feb 2026

CVE-2025-36595: Dell Unisphere for PowerMax vApp · Static Code Injection

Affects Dell Unisphere for PowerMax vAppSource CVE Database V5

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Dell Unisphere for PowerMax vApp	Affected =9.2.4	Fixed in–

AI-suggested

Until an official patch is released by Dell, organizations should implement several specific mitigations to reduce risk. First, restrict remote access to the Unisphere for PowerMax vApp management interfaces using network segmentation, VPNs, or firewall rules to limit exposure only to trusted administrative hosts. Second, enforce strict access controls and multi-factor authentication for all high-privileged accounts to prevent unauthorized access. Third, monitor logs and network traffic for unusual activities indicative of exploitation attempts, such as unexpected code execution or configuration changes. Fourth, conduct regular audits of privileged user activities to detect potential insider threats. Fifth, consider deploying application-layer firewalls or intrusion detection/prevention systems tuned to detect anomalous commands or code injection patterns targeting the management interface. Finally, maintain up-to-date backups of critical configurations and data to enable recovery in case of compromise. Once Dell releases patches, prioritize their deployment in accordance with organizational change management policies. Additionally, engage with Dell support and subscribe to security advisories to stay informed about updates and exploit developments.

Description

Dell Unisphere for PowerMax vApp, version(s) 9.2.4.x, contain(s) an Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Code execution.

Impact

The exploitation of CVE-2025-36595 could have severe consequences for organizations relying on Dell PowerMax storage solutions. Arbitrary code execution within the storage management environment can lead to unauthorized data access, modification, or deletion, severely impacting data confidentiality and integrity. Additionally, attackers could disrupt storage operations, causing availability issues that affect business continuity and critical applications dependent on the storage arrays. Given the central role of PowerMax systems in enterprise data centers, such disruptions could cascade into broader IT infrastructure outages. The requirement for high privileges and remote access limits the attack surface but also means that insider threats or compromised administrative accounts pose a significant risk. The absence of known exploits in the wild currently reduces immediate threat levels, but the vulnerability's nature and impact potential make it a prime target for attackers once exploit code becomes available. Organizations could face regulatory and compliance repercussions if sensitive data is compromised due to this vulnerability. Overall, the threat affects confidentiality, integrity, and availability, making it a critical concern for enterprises with PowerMax deployments worldwide.

CWE-96Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
Perform proper output validation and escaping to neutralize all code syntax from data written to code files.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.2.8 (opens in a new tab)
V5.2.5 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
User-Controlled Filename (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
AJAX Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

dell.com/support/kbdoc/en-us/000337554/dsa-2025-235-dell-powermaxos-dell-powermax-eem-dell-unisphere-for-powermax-dell-unisphere-for-powermax-virtual-appliance-dell-unisphere-360-dell-solutions-enabler-and-dell-solutions-enabler-virtual-appliance-security-update-for-multiple-vulnerabilit (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 01:49 UTC

WeaknessesCWE-96

Technical details

References

Community reviews

Related threats