CVE-2026-26943
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, versions 7.7.1.0 through 8.6, LTS2025 release version 8.3.1.0 through 8.3.1.20, LTS2024 release versions 7.13.1.0 through 7.13.1.60 contain an OS command injection vulnerability. A high privileged attacker with remote 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 in versions 7.7.1.0 through 8.6, LTS2025 (8.3.1.0-8.3.1.20), and LTS2024 (7.13.1.0-7.13.1.60). A high-privileged attacker with remote access can inject arbitrary OS commands that execute with root privileges due to insufficient input sanitization in the affected component.
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< 2.7.9>= 7.7.1.0, < 7.13.1.70>= 7.14.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the Dell Data Domain systemLog into the appliance CLI and run 'system show' or check the system model/metadata to confirm it is a Dell PowerProtect Data Domain or Dell Data Domain applianceAffected if The system is not a Dell Data Domain product - this CVE does not apply
-
Determine the installed Data Domain OS versionRun the command to display the DDOS version, typically via 'version' or 'system show version' in the appliance CLIAffected if The version command fails or returns an unrecognized format indicating a non-DDOS system
-
Compare installed version against affected rangesCheck if the installed version falls within: 7.7.1.0 through 7.13.1.69, 7.14.0.0 through 8.3.1.29, or 8.4.0.0 through 8.6.0.x. Use the exact version number returned by the version check.Affected if The installed version matches any of the affected 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.0)
-
Determine if remote administrative access is enabledReview the administrative access configuration via the management interface or CLI commands that show permitted remote access methods and IP restrictionsAffected if Remote administrative access (such as SSH or web management interfaces exposed to untrusted networks) is enabled and accessible
A user is affected if they run Dell Data Domain Operating System in any of the vulnerable version ranges with remote administrative access exposed to network attackers.
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 · scoped2.7.97.13.1.708.3.1.30
Apply Dell-supplied patches for this vulnerability; in the interim, restrict administrative access to trusted IP addresses only and monitor for unusual command execution patterns.
PowerProtect Dp Series Appliance: 2.7.9+ | Data Domain OS: 7.13.1.70+ or 8.3.1.30+ or 8.6.1.0+ (depending on current branch)
- 1. Identify the current installed version of PowerProtect Data Domain or Data Domain Operating System by running: admin$ version
- 2. For PowerProtect Dp Series Appliance: Upgrade to version 2.7.9 or later by downloading the ISO from Dell support portal and following the upgrade procedure in the product documentation
- 3. For Data Domain Operating System: If running 7.7.1.0-7.13.1.x, upgrade to version 7.13.1.70 or later
- 4. For Data Domain Operating System: If running 7.14.0.0-8.3.1.x, upgrade to version 8.3.1.30 or later
- 5. For Data Domain Operating System: If running 8.4.0.0-8.6.1.x, upgrade to version 8.6.1.0 or later
- 6. After upgrade, verify the new version is installed: admin$ version
- 7. Validate that the vulnerability is resolved by confirming the fixed version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26943 — 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-26943 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