CVE-2026-49813
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.7, LTS2026 release version 8.6.1.0 through 8.6.1.10, LTS2025 release version 8.3.1.0 through 8.3.1.30, LTS2024 release versions 7.13.1.0 through 7.13.1.70 contain an improper neutralization of special elements used in an OS command ('OS command Injection') vulnerability. A high privileged attacker with local 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 contains an OS command injection vulnerability (CWE-78) where improper neutralization of special elements in OS commands allows a high-privileged attacker with local system access to execute arbitrary commands on the underlying operating system.
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.7.1.0, <= 7.13.1.70>= 8.0.0.0, <= 8.3.1.30>= 8.4.0.0, <= 8.7.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify the Dell Data Domain systemLog into the Data Domain CLI or check the system model/hostname. Common commands include 'system show' or checking the management interface for the product name.Affected if The system is a Dell PowerProtect Data Domain or Dell Data Domain appliance.
-
Determine the installed Data Domain OS versionRun the version command on the Data Domain CLI, such as 'version' or 'show version'. This displays the operating system build and version number.Affected if A version number is returned indicating Dell Data Domain Operating System is installed.
-
Compare the installed version against the affected rangesMatch the installed version number to the vulnerable ranges: 7.7.1.0 through 7.13.1.70, 8.0.0.0 through 8.3.1.30, or 8.4.0.0 through 8.7.0.0.Affected if The installed version falls within any of these ranges: 7.7.1.0-7.13.1.70, 8.0.0.0-8.3.1.30, or 8.4.0.0-8.7.0.0.
-
Assess local access exposureVerify who has physical access or local shell access to the Data Domain system. Check user accounts with elevated privileges and confirm access controls are in place.Affected if Untrusted users or accounts have high-privileged local system access to the Data Domain operating system.
If the system is a Dell Data Domain running an OS version within 7.7.1.0-7.13.1.70, 8.0.0.0-8.3.1.30, or 8.4.0.0-8.7.0.0 and untrusted users have local access, it is affected by this command injection vulnerability.
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.
From vendor dataApply Dell-supplied patches for the affected versions (7.7.1.0-8.7, LTS2024 7.13.1.0-7.13.1.70, LTS2025 8.3.1.0-8.3.1.30, LTS2026 8.6.1.0-8.6.1.10) or upgrade to the latest patched release as specified in Dell Security Advisory DSA-2026-XXX.
- Consultation2.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49813 — 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-49813 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