CVE-2026-23778
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 remote 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 confidenceDell PowerProtect Data Domain appliances running DD OS contain a command injection vulnerability in multiple feature release and LTS versions. A high-privileged attacker with remote network access can inject operating system commands through the vulnerable interface, potentially executing them with root privileges on the underlying appliance OS.
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>= 7.14.0.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
- 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 DD OS versionRun 'ddos version' or 'system show version' on the Data Domain CLI to obtain the installed OS versionAffected if The installed version falls within any of these ranges: < 2.7.9 for DP Series Appliance; >= 7.7.1.0 and < 7.13.1.50; >= 7.14.0.0 and < 8.3.1.20; >= 8.4.0.0 and < 8.6.0.0 for DD OS
-
Confirm product modelRun 'hardware show' or check the system identifier to confirm whether the appliance is a PowerProtect DP Series or Data Domain systemAffected if The device is a PowerProtect DP Series Appliance or Data Domain system running a vulnerable DD OS version from step 1
-
Verify administrative network accessReview network access controls and firewall rules for the management interface. Check if remote administrative protocols (HTTPS, SSH) are exposed to untrusted networks using 'network show' or equivalent CLI commandsAffected if Remote network access to administrative interfaces is permitted from untrusted or external networks
-
Check for high-privilege accountsReview user accounts with administrative or root-level privileges using 'user list' or 'admin show' commands in DD OSAffected if Multiple high-privileged accounts exist and the system is network-accessible, increasing attack surface for this vulnerability
The environment is affected if the installed DD OS version or PowerProtect DP Series Appliance version matches any of the vulnerable version ranges listed and the management interface is network-accessible to potential 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.508.3.1.20
Apply Dell-provided patches or firmware updates to the latest supported DD OS version. Restrict administrative access to trusted networks and enforce least-privilege principles for administrative accounts until the patch can be deployed.
PowerProtect DP Series Appliance: 2.7.9 or later; Data Domain OS: 7.13.1.50+, 8.3.1.20+, or 8.6.0+ depending on original version branch
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'system show version' on the appliance console or via SSH
- 2. For PowerProtect DP Series Appliance: If version is below 2.7.9, upgrade to version 2.7.9 or later following the standard upgrade procedure in the Dell PowerProtect upgrade guide
- 3. For DD OS in range 7.7.1.0 to 7.13.1.50: Upgrade to DD OS version 7.13.1.50 or later
- 4. For DD OS in range 7.14.0.0 to 8.3.1.20: Upgrade to DD OS version 8.3.1.20 or later
- 5. For DD OS in range 8.4.0.0 to 8.6.0.0: Upgrade to DD OS version 8.6.0.0 or later
- 6. After upgrade, verify the new version using 'system show version' and confirm the command injection vulnerability is resolved
- 7. Review audit logs for any signs of exploitation attempts prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23778 — 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-23778 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