CVE-2026-24504
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 improper input validation 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 improper input validation vulnerability that allows a high-privileged attacker with remote access to execute arbitrary commands with root privileges. The vulnerability exists in versions 7.7.1.0 through 8.6, LTS2025 release versions 8.3.1.0 through 8.3.1.20, and LTS2024 release versions 7.13.1.0 through 7.13.1.60.
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 Dell Data Domain OS versionRun 'show version' from the Data Domain CLI or check the system management GUI under Administration > System OverviewAffected if Version is 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.5.x (any version below 8.6.1.0 in the 8.4+ branch)
-
Identify LTS release branchRun 'software show' or 'system show version' to confirm whether the system is running LTS2024 or LTS2025 release trainAffected if Running LTS2024 version 7.13.1.0 through 7.13.1.60, or LTS2025 version 8.3.1.0 through 8.3.1.20
-
Check PowerProtect DP Series Appliance versionAccess the PowerProtect DP appliance management interface and navigate to Settings > About, or run the appliance version command via SSHAffected if Appliance version is below 2.7.9
-
Confirm high-privileged remote access is configuredReview system access settings via 'access' commands in Data Domain CLI or check administrative user remote privileges in the management GUIAffected if Remote administrative/root access is enabled for users (the vulnerability requires high-privileged attacker with remote access)
The system is affected if running any Dell Data Domain OS version in the ranges 7.7.1.0-7.13.1.69, 7.14.0.0-8.3.1.29, or 8.4.0.0-8.6.0.x; or PowerProtect DP Series Appliance version below 2.7.9, AND the system allows remote high-privileged access.
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 patch or upgrade to a patched version as specified by Dell. Restrict high-privileged access to trusted users until the patch is applied.
PowerProtect DP Series Appliance: 2.7.9+ | Data Domain OS: 7.13.1.70+ / 8.3.1.30+ / 8.6.1.0+ depending on current branch
- For PowerProtect DP Series Appliance: Upgrade to version 2.7.9 or later
- For Data Domain Operating System: If running 7.7.1.0-7.13.1.x, upgrade to 7.13.1.70 or later
- For Data Domain Operating System: If running 7.14.0.0-8.3.1.x, upgrade to 8.3.1.30 or later
- For Data Domain Operating System: If running 8.4.0.0-8.6.1.x, upgrade to 8.6.1.0 or later
- After upgrade, verify the system is running the patched version and monitor for any unauthorized access attempts
- Consult Dell support for specific upgrade procedures and scheduling maintenance windows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24504 — 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-24504 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