CVE-2026-35073
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 · uneditedDell 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 confidenceDell PowerProtect Data Domain contains an OS command injection vulnerability (CWE-78) where improper neutralization of special elements in input allows a high-privileged attacker with local system access to inject and execute arbitrary OS commands with root privileges. The vulnerability affects multiple version ranges across standard releases and LTS branches.
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>= 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.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Data Domain OS versionUse the system management interface or run the command to display the OS version (e.g., via CLI: `version` or `system show version`)Affected if version falls within any of these ranges: >= 7.7.1.0 and < 7.13.1.70, OR >= 7.14.0.0 and < 8.3.1.30, OR >= 8.4.0.0 and <= 8.6.1.10, OR exactly 8.7.0.0
-
Determine if local console access is permittedReview system access controls to check whether local/physical console access is enabled for non-administrative or untrusted usersAffected if local or physical console access is available to any user beyond trusted high-privileged administrators
-
Verify privilege level of local usersList local user accounts and their assigned privilege levels using system user management commandsAffected if any untrusted or low-privilege local user accounts exist with potential console login capability
-
Review for suspicious root-level processesExamine running processes for unexpected commands executing as root (e.g., via process listing commands)Affected if unexpected or unauthorized commands are running with root privileges
You are affected if your Data Domain OS version is within the affected ranges AND local system access is possible for users other than trusted high-privileged administrators.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.13.1.708.3.1.30
Apply Dell vendor patches when released; until then, strictly limit local system access to trusted high-privileged administrators only, monitor for suspicious command execution, and consider network segmentation to reduce physical/logical local access exposure.
Upgrade to 7.13.1.70+ (LTS2024), 8.3.1.30+ (LTS2025), or 8.7.1.0+ depending on your current branch
- 1. Identify the currently installed Data Domain Operating System version using the admin console or CLI command 'system show version'
- 2. Determine which LTS track your current version belongs to (LTS2024 or LTS2025)
- 3. For LTS2024 track (7.13.x versions): Upgrade to version 7.13.1.70 or later
- 4. For LTS2025 track (8.3.x versions): Upgrade to version 8.3.1.30 or later
- 5. For 8.4.x through 8.6.x versions: Upgrade to version 8.7.1.0 or later (or the next available stable release)
- 6. For version 8.7.0.0: Upgrade to version 8.7.1.0 or later
- 7. Download the upgrade ISO from Dell Support (support.dell.com) using your service tag
- 8. Upload the upgrade package via the Data Domain Management Center or CLI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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