CVE-2026-35154
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 privilege management vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to elevation of privileges to access unauthorized delete operation.
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 confidenceDell PowerProtect Data Domain appliances contain an improper privilege management vulnerability where a high-privileged local attacker can escalate privileges to perform unauthorized delete operations. This is a local privilege escalation flaw affecting versions 7.7.1.0 through 8.7.0.0 and LTS releases.
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.13.1.0, < 7.13.1.70>= 8.3.0.0, < 8.3.1.30>= 8.4.0.0, < 8.6.1.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 Dell Data Domain OS versionAccess the Data Domain CLI and run the command to display the system version, such as 'version' or 'system show version', or check via the management interface under the system information sectionAffected if The displayed version falls within one of these ranges: 7.13.1.0 to 7.13.1.69, 8.3.0.0 to 8.3.1.29, or 8.4.0.0 to 8.6.0.9
-
Confirm the product is Data Domain Operating SystemVerify that the system is running Dell Data Domain Operating System (DDOS) and not another Dell product, as this vulnerability is specific to the Data Domain appliance lineAffected if The system is running Dell Data Domain Operating System
-
Determine if local user access existsCheck if local user accounts with high privileges exist on the system by reviewing user management settings or authentication configurationAffected if Local authenticated users with elevated privileges exist on the appliance
A system is affected if it runs Dell Data Domain Operating System version 7.13.1.0 through 7.13.1.69, 8.3.0.0 through 8.3.1.29, or 8.4.0.0 through 8.6.0.9 and has local user accounts with elevated privileges present.
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.308.6.1.0
Apply the vendor-supplied patch for Dell PowerProtect Data Domain to remediate the privilege management vulnerability; restrict local access to trusted administrators and follow least-privilege principles.
7.13.1.70 or later for LTS2024; 8.3.1.30 or later for LTS2025; 8.6.1.0 or later for 8.4.x/8.5.x releases
- 1. Identify the current Data Domain Operating System version by running 'system show version' or checking the management console
- 2. Based on the current version line, plan upgrade to the minimum fixed version: For 7.13.x line upgrade to 7.13.1.70 or later; For 8.3.x line upgrade to 8.3.1.30 or later; For 8.4.x/8.5.x line upgrade to 8.6.1.0 or later
- 3. Back up all critical data and configuration settings before initiating the upgrade
- 4. Schedule a maintenance window as upgrades require system downtime
- 5. Download the appropriate upgrade package from Dell Support (support.dell.com) for the PowerProtect Data Domain model
- 6. Follow Dell's standard upgrade procedure: upload the upgrade file via the management interface or CLI, then execute 'software upload' and 'software activate' commands
- 7. Verify the upgrade completed successfully by checking the version with 'system show version'
- 8. Confirm the vulnerability is remediated by ensuring the running version meets or exceeds the fixed versions listed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35154 — 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-35154 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