CVE-2026-23777
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 an exposure of sensitive information to an unauthorized actor vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to information exposure.
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 an information disclosure vulnerability where low-privileged remote users can access sensitive data they should not be authorized to view. The vulnerability exists across multiple Feature Release (7.7.1.0-8.5), LTS2025 (8.3.1.0-8.3.1.20), and LTS2024 (7.13.1.0-7.13.1.50) versions due to improper access controls.
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>= 7.13.1.0, <= 7.13.1.50>= 8.3.1.0, <= 8.3.1.20>= 7.7.1.0, <= 8.5.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 installed DD OS versionRun 'ddos -v' or 'system show version' on the Data Domain system to obtain the exact DD OS version numberAffected if The version falls within 7.7.1.0 through 8.5.0.0, or 8.3.1.0 through 8.3.1.20, or 7.13.1.0 through 7.13.1.50
-
Confirm the product modelRun 'hardware show' or check the system management interface to confirm the system is a Dell PowerProtect Data Domain or Dell Data Domain applianceAffected if The system is a PowerProtect Data Domain or Data Domain model running the affected DD OS versions
-
Check if remote management access is enabledReview the DD OS network configuration using 'network show' or check the management interface settings for enabled remote access protocols (HTTP/HTTPS/SSH)Affected if Remote management access is enabled and the system is running an affected DD OS version
-
Review low-privilege user accountsUse 'user list' or access the DD OS user management interface to enumerate existing user accounts and their assigned rolesAffected if Low-privilege user accounts exist on a system running an affected DD OS version
The environment is affected if it runs Dell PowerProtect Data Domain or Data Domain systems with DD OS versions 7.7.1.0-8.5.0.0, 8.3.1.0-8.3.1.20, or 7.13.1.0-7.13.1.50 and has remote access enabled with low-privilege users present.
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 · scopedApply the vendor-supplied patch or upgrade to a fixed DD OS version to remediate the unauthorized information exposure. Review user access permissions and role assignments as part of remediation.
LTS2024: 7.13.1.51 or later; LTS2025: 8.3.1.21 or later; Feature Release: 8.6 or later (or latest available LTS with fix)
- 1. Identify the currently installed Data Domain Operating System (DD OS) version using the 'version' command or through the DD Web UI.
- 2. Determine which release track the system is on: LTS2024 (7.13.x), LTS2025 (8.3.x), or Feature Release (7.7.x - 8.5.x).
- 3. For LTS2024 (7.13.1.0 - 7.13.1.50): Upgrade to LTS2024 release version 7.13.1.51 or later, or migrate to a newer LTS release.
- 4. For LTS2025 (8.3.1.0 - 8.3.1.20): Upgrade to LTS2025 release version 8.3.1.21 or later, or migrate to a newer LTS release.
- 5. For Feature Release (7.7.1.0 - 8.5.0.0): Upgrade to Feature Release 8.6 or later if available, or migrate to an LTS release with the fix.
- 6. After upgrade, verify the new version is not within the affected ranges.
- 7. Review DD OS security settings and ensure low-privileged user access controls are properly configured according to Dell best practices.
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-23777 — 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-23777 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