Data Domain Operating SystemOperating system · Dell

CVE-2026-41122

HIGH · 7.1 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 7.13.1.80 / 8.3.1.40 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 6 weeks old

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 · unedited
Dell 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 a stored cross-site scripting vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability. Exploitation may lead to information disclosure, session theft, or client-side request forgery.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in Dell PowerProtect Data Domain. An unauthenticated remote attacker can inject malicious scripts into the application that are persistently stored and executed when other users access the compromised data, leading to information disclosure, session hijacking, or client-side request forgery.

MitigationApply the vendor-supplied patches or upgrade to a non-vulnerable version as specified in Dell's security advisory. Validate that all affected versions have been patched.

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
Data Domain Operating SystemOperating system
Affected:>= 7.7.1.0, < 7.13.1.80>= 7.14.0.0, < 8.3.1.40>= 8.4.0.0, < 8.6.1.20>= 8.7.0.0, < 8.8.0.0

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Data Domain OS version
    Access the Data Domain CLI or web management interface and retrieve the system version. In CLI, this is typically obtained via the 'version' or 'system show version' command.
    Affected if The installed version falls within any of the affected ranges: >= 7.7.1.0 and < 7.13.1.80; OR >= 7.14.0.0 and < 8.3.1.40; OR >= 8.4.0.0 and < 8.6.1.20; OR >= 8.7.0.0 and < 8.8.0.0
  2. Verify web management interface is accessible
    Determine if the Data Domain web interface is network-accessible. This can be confirmed by reviewing network exposure, firewall rules, or attempting to reach the web portal.
    Affected if The web interface is exposed to network users, as the stored XSS vulnerability is exploited through the application web interface
  3. Identify authentication mechanism in use
    Check whether unauthenticated access to the application is possible, as the CVE specifies an unauthenticated attacker can inject the malicious scripts.
    Affected if Unauthenticated or weakly authenticated access to the web interface is permitted, allowing the attack vector described

The environment is affected if the Data Domain OS version falls within any of the four vulnerable version ranges and the web interface is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.13.1.80 / 8.3.1.40 / 8.6.1.20 or later
Fixed in 7.13.1.808.3.1.408.6.1.20
Interim mitigation

Apply the vendor-supplied patches or upgrade to a non-vulnerable version as specified in Dell's security advisory. Validate that all affected versions have been patched.

Recommended fix High confidence

8.8.0.0 or later (or the appropriate minimum fixed version for your branch: 7.13.1.80, 8.3.1.40, or 8.6.1.20)

  1. 1. Identify the current Data Domain Operating System version using the system CLI or management interface
  2. 2. If running version >= 7.7.1.0 and < 7.13.1.80, upgrade to version 7.13.1.80 or later
  3. 3. If running version >= 7.14.0.0 and < 8.3.1.40, upgrade to version 8.3.1.40 or later
  4. 4. If running version >= 8.4.0.0 and < 8.6.1.20, upgrade to version 8.6.1.20 or later
  5. 5. If running version >= 8.7.0.0 and < 8.8.0.0, upgrade to version 8.8.0.0 or later
  6. 6. After upgrade, verify the new version is correctly installed and the web interface is functional
  7. 7. Test the application to confirm the XSS vulnerability is remediated
Caveat Review Dell upgrade documentation for your version path; some upgrades may require downtime and specific upgrade procedures

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41122 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41122 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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