CVE-2026-23853
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 use of weak credentials vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to unauthorized access to the system.
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 versions 7.7.1.0 through 8.5, LTS2025 versions 8.3.1.0-8.3.1.20, and LTS2024 versions 7.13.1.0-7.13.1.50 contain weak default credentials that allow an unauthenticated attacker with local physical or console access to gain unauthorized system access.
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.30>= 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Determine DD OS versionAccess the Data Domain console or CLI and run the command to display the system version (for example, 'version' or 'system show version'). Compare the output against the affected ranges: 7.7.1.0 to 7.13.1.59, 7.14.0.0 to 8.3.1.29, or 8.4.0.0 to 8.6.0.0.Affected if The installed version falls within any of the affected ranges listed.
-
Determine PowerProtect DP Series Appliance versionAccess the PowerProtect DP Series management interface or console and retrieve the firmware/software version. Compare against the affected range: versions earlier than 2.7.9.Affected if The installed version is lower than 2.7.9.
-
Verify default credentials are changedReview the system's user account configuration through the management console or CLI. Check if the default administrative accounts (such as 'admin' or similar built-in accounts) still use their factory default passwords.Affected if Default administrative accounts retain their original default passwords.
You are affected if your system runs a vulnerable DD OS or PowerProtect DP Series version AND default credentials have not been changed from the factory settings.
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.30
Apply vendor-provided patches or upgrade to a fixed DD OS version; immediately change any default credentials to strong, unique passwords if patching is delayed.
PowerProtect DP Series Appliance: 2.7.9 or later | DD OS: 7.13.1.60, 8.3.1.30, or 8.6.0.1 (or latest stable) depending on current branch
- 1. Identify the current installed version of PowerProtect DP Series Appliance or Data Domain Operating System (DD OS) using the system management interface or CLI command 'version'.
- 2. For PowerProtect DP Series Appliance: If version is below 2.7.9, schedule a maintenance window and upgrade to version 2.7.9 or later.
- 3. For Data Domain OS: Determine which version branch is currently installed (7.7.x, 7.13.x, 7.14.x, 8.3.x, or 8.4.x-8.6.x).
- 4. For DD OS 7.7.1.0-7.13.1.60: Upgrade to version 7.13.1.60 or later (but before 7.14.0.0).
- 5. For DD OS 7.14.0.0-8.3.1.30: Upgrade to version 8.3.1.30 or later (but before 8.4.0.0).
- 6. For DD OS 8.4.0.0-8.6.0.0: Upgrade to version 8.6.0.1 or later, or to the latest stable 8.x release.
- 7. After upgrade, verify the system is running the patched version using 'version' command.
- 8. Review and change any default credentials as part of post-upgrade hardening.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23853 — 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-23853 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