dbcve.org
PowerstoreosOperating system · Dell

CVE-2026-28265

HIGH · 7.1 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 4.4.0.0-2692403 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PowerStore, contains a Path Traversal vulnerability in the Service user. A low privileged attacker with local access could potentially exploit this vulnerability, leading to modification of arbitrary system files.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Dell PowerStore storage systems contain a path traversal vulnerability in the Service user component. A low-privileged attacker with local access to the system can manipulate file path inputs to escape intended directory constraints and write to or modify arbitrary system files outside the intended scope.

MitigationApply the vendor-provided security patch or firmware update for PowerStore that addresses the path traversal vulnerability. Additionally, restrict local access to trusted personnel and implement file system access controls to limit the Service user's permissions to only required directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PowerstoreosOperating system
Affected:< 4.4.0.0-2692403

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the PowerStoreOS version
    Access the PowerStore system management interface or CLI and retrieve the installed PowerStoreOS version. This is typically found in the system diagnostics, firmware information, or via the 'storage system show' command in the PowerStore CLI.
    Affected if The installed version is lower than 4.4.0.0-2692403 (e.g., 4.3.x.x, 4.2.x.x, etc.)
  2. Confirm the system is a Dell PowerStore storage array
    Verify the hardware model and system type through the PowerStore management UI, BIOS information, or the 'system show' command in the PowerStore CLI to confirm it is a Dell PowerStore device.
    Affected if The system is a Dell PowerStore storage array and the PowerStoreOS version is below 4.4.0.0-2692403
  3. Verify the Service user component exists and is accessible
    Check if the Service user account is configured on the PowerStore system through the user management section of the PowerStore UI or via the 'user show' command listing all local users.
    Affected if The Service user account exists on the system running a vulnerable PowerStoreOS version
  4. Review file system access logs for the Service user
    Examine PowerStore audit logs, system event logs, or file access logs for any file write or path manipulation operations performed by the Service user, looking for paths that escape expected directories.
    Affected if There are log entries showing the Service user accessing paths outside expected directories, or creating/modifying files in system locations outside the intended scope

A user is affected if they are running Dell PowerStore with PowerStoreOS version lower than 4.4.0.0-2692403 and the Service user component is present on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.0.0-2692403 or later
Fixed in 4.4.0.0-2692403
Interim mitigation

Apply the vendor-provided security patch or firmware update for PowerStore that addresses the path traversal vulnerability. Additionally, restrict local access to trusted personnel and implement file system access controls to limit the Service user's permissions to only required directories.

Recommended fix Moderate confidence

PowerStoreOS 4.4.0.0-2692403 or later

  1. 1. Back up all critical data and configuration on the PowerStore system
  2. 2. Review Dell PowerStore release notes for version 4.4.0.0-2692403 to understand new features and any prerequisites
  3. 3. Contact Dell Technical Support to obtain the upgrade package and validate upgrade path from your current version
  4. 4. Schedule a maintenance window as upgrades may require system downtime
  5. 5. Follow Dell's documented upgrade procedure for PowerStoreOS, typically via the PowerStore Manager UI or CLI
  6. 6. After upgrade, verify the system is running version 4.4.0.0-2692403 or later
  7. 7. Confirm the path traversal vulnerability is resolved by validating the Service user cannot access/modify arbitrary system files
Caveat Enterprise storage upgrades may have compatibility considerations; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerstoreos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28265 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data