CVE-2026-23774
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.10, LTS2024 release versions 7.13.1.0 through 7.13.1.40, contain an OS command injection vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to arbitrary command execution.
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 running DD OS contains an OS command injection vulnerability in Feature Release versions 7.7.1.0 through 8.5, LTS2025 release versions 8.3.1.0 through 8.3.1.10, and LTS2024 release versions 7.13.1.0 through 7.13.1.40. An authenticated high-privileged attacker with remote network access can inject arbitrary OS commands through the DD OS interface, achieving full command execution on the underlying operating system.
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 the product and OS versionAccess the DD OS command-line interface (CLI) or management console and run the command to display the system version, typically 'system show version' or check the About/Version section in the management GUIAffected if The installed DD OS version falls within 7.7.1.0 through 7.13.1.49, 7.14.0.0 through 8.3.1.19, or 8.4.0.0 through 8.5.x (or the DP Series Appliance version is below 2.7.9)
-
Confirm DD OS is accessible over the networkVerify that the DD OS management interface (typically HTTPS on port 443) is exposed to the network and reachable from untrusted segmentsAffected if The DD OS management interface is reachable from network segments accessible to untrusted users, as the vulnerability requires remote network access
-
Identify high-privileged accountsCheck the list of configured administrative users in DD OS using 'user list' or through the management interface User Administration sectionAffected if There are multiple high-privileged administrative accounts, as an authenticated attacker with such privileges can exploit the vulnerability
The environment is affected if the installed Dell Data Domain OS version or DP Series Appliance version falls within the affected ranges AND the DD OS management interface is network-accessible to an authenticated high-privileged user.
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 security patches or upgrade to the patched DD OS version as specified in Dell's security advisory. Limit administrative access to trusted personnel only and implement network segmentation to reduce attack surface.
DD OS 7.13.1.50+, 8.3.1.20+, 8.6.0.0+ or PowerProtect DP 2.7.9+ (specific version depends on your current release branch)
- Contact Dell Support or visit Dell's support portal to obtain the specific patch/upgrade for your Data Domain OS version
- For PowerProtect DP Series Appliance: upgrade to version 2.7.9 or later
- For DD OS 7.7.1.x - 7.13.1.x: upgrade to version 7.13.1.50 or later
- For DD OS 7.14.0.x - 8.3.1.x: upgrade to version 8.3.1.20 or later
- For DD OS 8.4.0.x - 8.5.x: upgrade to version 8.6.0.0 or later
- For LTS2024 (7.13.1.x): upgrade to version 7.13.1.50 or later
- For LTS2025 (8.3.1.x): upgrade to version 8.3.1.20 or later
- After upgrade, verify the fix by checking DD OS version and reviewing release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23774 — 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-23774 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