CVE-2026-24506
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 as root.
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 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) contain an OS command injection vulnerability allowing a high-privileged remote attacker to execute arbitrary commands as root.
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.
-
Check Data Domain OS versionAccess the Data Domain management console or CLI and run the 'version' command to display the installed DDOS versionAffected if The installed version is 7.7.1.0 through 7.13.1.69, or 7.14.0.0 through 8.3.1.29, or 8.4.0.0 through 8.5.x (any version below 8.6.1.0 but above 8.4.0.0)
-
Check PowerProtect DP Series Appliance versionAccess the PowerProtect DP appliance management interface and locate the version information in the system or about sectionAffected if The installed version is below 2.7.9
-
Verify remote administrative access configurationReview network settings and access controls for the Data Domain management interface. Check if remote access for privileged administrators is enabled and exposed to networkAffected if Remote administrative access is enabled and the management interface is accessible from external or untrusted networks
-
Inspect for unauthorized root-level processesExecute 'ps -ef | grep root' via console or authorized session to list root-owned processes. Check for unexpected or unknown processesAffected if Unfamiliar processes running as root that are not part of standard Data Domain operations are present
-
Check for suspicious files in temp directoriesExamine /tmp, /var/tmp, and other writable directories for unknown executables or scripts using 'ls -la'Affected if Unexpected binaries, scripts, or files with random names exist in these directories
You are affected if your Dell Data Domain OS version is 7.7.1.0-7.13.1.69, 7.14.0.0-8.3.1.29, or 8.4.0.0-8.5.x, or your PowerProtect DP Series Appliance is below version 2.7.9, AND remote privileged access is available to 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 the vendor-supplied patch or upgrade to a fixed version outside the affected version ranges. Limit privileged remote access and monitor for indicators of compromise until remediation is complete.
Dell PowerProtect Data Domain: 7.13.1.70 (for 7.13.x branch), 8.3.1.30 (for 8.3.x branch), 8.6.1.0 (for 8.4.x/8.6.x branch); PowerProtect DP Series Appliance: 2.7.9
- 1. Identify the current version of the Dell PowerProtect Data Domain or PowerProtect DP Series Appliance by running 'ddr version' or checking the system management interface
- 2. Determine which version branch your system is running: 7.13.x, 8.3.x, or 8.6.x
- 3. For systems on the 7.13.x branch (versions 7.13.1.0-7.13.1.60): upgrade to version 7.13.1.70 or later
- 4. For systems on the 8.3.x branch (versions 8.3.1.0-8.3.1.20): upgrade to version 8.3.1.30 or later
- 5. For systems on the 8.4.x/8.6.x branch (versions 8.4.0.0-8.6.0.x): upgrade to version 8.6.1.0 or later
- 6. For PowerProtect DP Series Appliance (versions before 2.7.9): upgrade to version 2.7.9 or later
- 7. After upgrade, verify the new version is running and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24506 — 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-24506 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