dbcve.org
Powerprotect Dp Series ApplianceApplication · Dell

CVE-2026-35074

MEDIUM · 6.7 CVSS v3.1 Published 2026-04-17
Fix available
A fix is available. Upgrade to 2.7.9 / 7.13.1.70 or later.
See remediation →
69/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
Dell PowerProtect Data Domain Feature Release versions 7.7.1.0 through 8.6.0.0 and version 8.7.0.0, LTS2025 release versions 8.3.1.0 through 8.3.1.20, and LTS2024 release versions 7.13.1.0 through 7.13.1.60 contain an improper neutralization of special elements used in an OS Command Injection vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to arbitrary command execution with root privileges.

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 · high confidence

Dell PowerProtect Data Domain contains an OS command injection vulnerability due to improper neutralization of special elements in input. A high-privileged attacker with local access can exploit this to execute arbitrary commands with root privileges.

MitigationApply the vendor-supplied patches for the affected versions (7.7.1.0-8.7.0.0, LTS2025 8.3.1.0-8.3.1.20, LTS2024 7.13.1.0-7.13.1.60) to remediate the command injection flaw.

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
Powerprotect Dp Series ApplianceApplication
Affected:< 2.7.9
Data Domain Operating SystemOperating system
Affected:>= 7.7.1.0, < 7.13.1.70>= 7.14.0.0, < 8.3.1.30>= 8.4.0.0, <= 8.6.1.10= 8.7.0.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/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 installed product and version
    Run the command to display the Data Domain or PowerProtect appliance system version (e.g., 'software show' or check the system management interface for the OS version)
    Affected if The version displayed is lower than 2.7.9 for PowerProtect DP Series, or falls within the DDOS ranges 7.7.1.0-7.13.1.69, 7.14.0.0-8.3.1.29, 8.4.0.0-8.6.1.10, or equals exactly 8.7.0.0
  2. Confirm the exact DDOS version number
    Use 'version' or 'system show version' command on the Data Domain CLI, or check the About/System Info page in the management GUI
    Affected if The version begins with 7.7, 7.8, 7.9, 7.10, 7.11, 7.12, 7.13 (below .70), 7.14, 7.15, 8.0, 8.1, 8.2, 8.3 (below .30), 8.4, 8.5, 8.6 (at or below .10), or 8.7.0.0 exactly
  3. Verify PowerProtect DP Appliance version
    Check the DP Series Appliance version through the management console or CLI (e.g., 'show system' or 'version' command)
    Affected if The installed DP Series Appliance version is any version prior to 2.7.9 (for example, 2.7.8, 2.7.0, 2.6.x, etc.)
  4. Determine if local privileged access exists
    Review which accounts have root or administrative privileges on the system, and verify which users can access the local console or SSH with high-privileged credentials
    Affected if The system allows local high-privileged accounts that could potentially exploit the command injection flaw (this condition is satisfied for any affected version above)

You are affected if your Dell PowerProtect DP Series Appliance is below version 2.7.9, or your Dell Data Domain Operating System version is within any of the ranges: 7.7.1.0-7.13.1.69, 7.14.0.0-8.3.1.29, 8.4.0.0-8.6.1.10, or exactly 8.7.0.0.

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 2.7.9 / 7.13.1.70 / 8.3.1.30 or later
Fixed in 2.7.97.13.1.708.3.1.30
Interim mitigation

Apply the vendor-supplied patches for the affected versions (7.7.1.0-8.7.0.0, LTS2025 8.3.1.0-8.3.1.20, LTS2024 7.13.1.0-7.13.1.60) to remediate the command injection flaw.

Recommended fix Moderate confidence

PowerProtect DP Series Appliance: 2.7.9+ | Data Domain OS: 7.13.1.70+, 8.3.1.30+, 8.6.1.20+, or latest 8.8.x+

  1. 1. Identify the exact Data Domain Operating System (DDOS) version currently installed using the 'version' command or via the DD Management Console
  2. 2. For PowerProtect DP Series Appliance: Upgrade to version 2.7.9 or later from Dell support portal
  3. 3. For Data Domain OS: Determine which version branch you are on (7.7.x, 7.13.x, 7.14.x, 8.3.x, 8.4.x, 8.5.x, 8.6.x, or 8.7.x)
  4. 4. For DDOS 7.7.x - 7.13.x: Upgrade to version 7.13.1.70 or later
  5. 5. For DDOS 7.14.x - 8.3.x: Upgrade to version 8.3.1.30 or later
  6. 6. For DDOS 8.4.x - 8.6.x: Upgrade to version 8.6.1.20 or later (if available) or migrate to a supported release
  7. 7. For DDOS 8.7.x: Upgrade to the latest available DDOS release (8.8.x or later recommended)
  8. 8. Schedule maintenance window and backup current configuration
Caveat Review Dell upgrade guide for compatibility requirements; some upgrades may require intermediate steps if jumping multiple major versions

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

Fix this in Powerprotect Dp Series Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35074 — 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-35074 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