CVE-2026-23779
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 with Data Domain Operating System (DD OS) of Feature Release versions 7.7.1.0 through 8.5, LTS2025 release version 8.3.1.0 through 8.3.1.20, LTS2024 release versions 7.13.1.0 through 7.13.1.50, contain a command injection vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability to gain root-level access.
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 confidenceCommand injection vulnerability in Dell PowerProtect Data Domain's Data Domain Operating System (DD OS) allows a high-privileged local attacker to inject arbitrary commands and escalate to root-level access. The vulnerability affects multiple feature release and LTS versions.
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.50>= 8.3.1.0, < 8.3.1.20>= 8.4.0.0, < 8.6.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 the installed productRun 'system show model' or check the appliance model number to determine if it is a Dell PowerProtect DP Series Appliance or a Dell Data Domain system running DD OSAffected if Product is Dell PowerProtect DP Series Appliance or Dell Data Domain Operating System
-
Check DD OS versionRun 'version' or 'show version' command on the DD OS CLI to obtain the exact firmware version numberAffected if Version cannot be determined or is not displayed
-
Compare PowerProtect DP Appliance versionIf running PowerProtect DP Series Appliance, run 'software show' or check the management interface for the installed version. Affected if version < 2.7.9Affected if PowerProtect DP Series Appliance version is below 2.7.9
-
Compare DD OS version against first rangeIf running DD OS, check if version is >= 7.7.1.0 and < 7.13.1.50. Run 'version' to see the full version stringAffected if DD OS version falls within >= 7.7.1.0 and < 7.13.1.50
-
Compare DD OS version against second rangeCheck if DD OS version is >= 8.3.1.0 and < 8.3.1.20Affected if DD OS version falls within >= 8.3.1.0 and < 8.3.1.20
-
Compare DD OS version against third rangeCheck if DD OS version is >= 8.4.0.0 and < 8.6.0.0Affected if DD OS version falls within >= 8.4.0.0 and < 8.6.0.0
The environment is affected if it is a Dell PowerProtect DP Series Appliance below version 2.7.9, or Dell Data Domain Operating System with a version matching any of the three affected ranges (7.7.1.0-7.13.1.49, 8.3.1.0-8.3.1.19, or 8.4.0.0-8.5.9.x).
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.508.3.1.20
Apply vendor patches for the affected DD OS versions. Restrict local access to trusted, privileged users only and monitor for suspicious local activity.
PowerProtect DP Series Appliance: upgrade to 2.7.9 or later; DD OS: upgrade to 7.13.1.50, 8.3.1.20, or 8.6.0.0 (depending on current branch)
- 1. Identify the currently installed PowerProtect DP Series Appliance or Data Domain Operating System version using the system management interface or CLI.
- 2. For PowerProtect DP Series Appliance: If version is below 2.7.9, plan upgrade to version 2.7.9 or later.
- 3. For Data Domain Operating System: Determine which version range applies (7.7.x, 8.3.x, or 8.4.x-8.5.x) and upgrade to the corresponding fixed version: 7.13.1.50, 8.3.1.20, or 8.6.0.0 respectively.
- 4. Review Dell upgrade documentation and release notes for the target version before initiating upgrade.
- 5. Schedule maintenance window as upgrades may require system downtime.
- 6. Perform backup of critical configuration data as a precautionary measure.
- 7. Execute upgrade following Dell-provided procedures for the specific appliance/model.
- 8. Verify successful installation by confirming the new version post-upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-23779 — 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-23779 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