CVE-2026-26354
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 Domain Operating System (DD OS) of Feature Release versions 7.7.1.0 through 8.6, LTS2025 release version 8.3.1.0 through 8.3.1.10, LTS2024 release versions 7.13.1.0 through 7.13.1.60, contain a stack-based Buffer Overflow vulnerability. An unauthenticated 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 systems running DD OS contain a stack-based buffer overflow vulnerability in Feature Release versions 7.7.1.0 through 8.6, LTS2025 release versions 8.3.1.0 through 8.3.1.10, and LTS2024 release versions 7.13.1.0 through 7.13.1.60. An unauthenticated attacker with network access can exploit this buffer overflow to achieve arbitrary command execution on the affected appliance.
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.60>= 7.14.0.0, < 8.3.1.20>= 8.4.0.0, < 8.6.1.10CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 DD OS versionAccess the Data Domain management console or use the CLI command `system show version` to retrieve the installed DD OS version number.Affected if The installed version falls within 7.7.1.0 through 7.13.1.59, OR 7.14.0.0 through 8.3.1.19, OR 8.4.0.0 through 8.6.0.x (any build before 8.6.1.10). Compare your version against these ranges to confirm if it is affected.
-
Confirm the PowerProtect DP Appliance firmware versionIf using a PowerProtect DP Series Appliance, check the appliance firmware version through the management interface or `fwver` command.Affected if The firmware version is below 2.7.9.
-
Verify network accessibility of management interfacesReview the network configuration to determine if Data Domain management interfaces (HTTPS, SSH, or other management ports) are exposed to untrusted or external networks.Affected if The management interface is reachable from untrusted networks or the internet without proper network segmentation or access controls.
-
Check for direct external exposureScan or review firewall rules to confirm whether ports used for Data Domain management (typically 22, 443, or vendor-specified ports) are open to the public internet or non-segmented network zones.Affected if Management ports are open to the internet or untrusted external networks, enabling an unauthenticated attacker to reach the vulnerable service.
The environment is affected if the DD OS version is 7.7.1.0 to 7.13.1.59, 7.14.0.0 to 8.3.1.19, or 8.4.0.0 to 8.6.0.x (or the DP Appliance firmware is below 2.7.9), AND the management interface is network-accessible to unauthenticated 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.608.3.1.20
Apply vendor-supplied patches for the specific DD OS version (upgrade to 8.7 or later for Feature Release, 8.3.1.11 or later for LTS2025, 7.13.1.61 or later for LTS2024). Implement network segmentation and restrict external access to the Data Domain management interfaces until patching can be completed.
PowerProtect DP: 2.7.9+ | DD OS: 7.13.1.60+ (7.7.1-7.13 branch), 8.3.1.20+ (7.14-8.3 branch), 8.6.1.10+ (8.4-8.6 branch)
- 1. Identify the currently installed PowerProtect DP Appliance or Data Domain Operating System version using the system CLI or management interface.
- 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 OS on 7.7.1.0 through 7.13.x branch: Upgrade to version 7.13.1.60 or later.
- 4. For Data Domain OS on 7.14.0.0 through 8.3.x branch: Upgrade to version 8.3.1.20 or later.
- 5. For Data Domain OS on 8.4.0.0 through 8.6.x branch: Upgrade to version 8.6.1.10 or later.
- 6. Verify the upgrade was successful by confirming the new version meets the fixed release criteria.
- 7. Test that critical Data Domain operations (backup, replication, deduplication) function normally 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-26354 — 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-26354 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