CVE-2026-23775
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 appliances with Data Domain Operating System (DD OS) of Feature Release versions 8.0 through 8.5, LTS2025 release version 8.3.1.0 through 8.3.1.10 contain an insertion of sensitive information into log file vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to credential exposures. Authentication attempts as the compromised user would need to be authorized by a high privileged DD user. This vulnerability only affects systems with retention lock enabled.
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 · moderate confidenceA log injection vulnerability in Dell PowerProtect Data Domain appliances running DD OS versions 8.0-8.5 and 8.3.1.0-8.3.1.10 allows a low-privileged remote attacker to insert sensitive information, specifically credentials, into log files. This only affects systems with retention lock enabled.
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>= 8.3.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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
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 appliance and DD OS versionRun command 'ddos-version' or check the system dashboard for the Data Domain model and DD OS version. The product should be Dell PowerProtect Data Domain running DD OS.Affected if The system is a Dell PowerProtect Data Domain appliance running DD OS version 8.3.0.0-8.3.1.19 or 8.4.0.0-8.5.x
-
Verify if retention lock is enabledRun command 'retention lock status' or check the Data Domain management interface for retention lock configuration. Retention lock must be enabled for this vulnerability to be exploitable.Affected if Retention lock is currently enabled on the system
-
Confirm remote access configurationCheck if the system allows remote network connections. Review the access settings via 'ddos-cli' or the management interface for remote authentication and access policies.Affected if The system accepts remote network connections from low-privileged users
A system is affected only if it is a Dell PowerProtect Data Domain running a vulnerable DD OS version (8.3.0.0-8.3.1.19 or 8.4.0.0-8.5.x) AND has retention lock enabled AND permits remote 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 · scoped8.3.1.208.6.0.0
Apply vendor-provided patches from Dell for affected DD OS versions. Until patched, ensure systems with retention lock enabled have enhanced log monitoring to detect unauthorized access patterns.
DD OS 8.3.1.20 or later for LTS2025 releases; DD OS 8.6.0.0 or later for Feature Release 8.4/8.5
- 1. Verify current Data Domain Operating System version by running 'system show version' on the DD CLI
- 2. Confirm retention lock is enabled by running 'retention lock show' - note this vulnerability only affects systems with retention lock enabled
- 3. Schedule a maintenance window for the upgrade
- 4. Download the appropriate DD OS upgrade bundle from Dell Support (www.dell.com/support) for your model
- 5. Upload the upgrade bundle to the Data Domain system using 'software upload <filename.tar>'
- 6. Verify the uploaded software using 'software verify <filename.tar>'
- 7. Install the upgrade using 'software install <filename.tar>' and follow the on-screen prompts
- 8. After installation completes, verify the new version with 'system show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23775 — 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-23775 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