Powerprotect Data ManagerApplication · Dell

CVE-2026-22267

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 19.22 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Manager, version(s) prior to 19.22, contain(s) an Incorrect Privilege Assignment vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Elevation of privileges.

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

Dell PowerProtect Data Manager versions prior to 19.22 contain an Incorrect Privilege Assignment vulnerability that allows a low privileged attacker with remote access to escalate privileges to higher authority levels on the affected system.

MitigationUpgrade Dell PowerProtect Data Manager to version 19.22 or later to remediate this vulnerability. If immediate upgrading is not possible, restrict network access to trusted users and monitor for unauthorized privilege escalation attempts.

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
Powerprotect Data ManagerApplication
Affected:< 19.22

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify PowerProtect Data Manager version
    Access the product administration interface or check system information to determine the exact installed version number
    Affected if Installed version is lower than 19.22
  2. Determine remote access exposure
    Review network configuration and access settings to determine if remote access to PowerProtect Data Manager is enabled
    Affected if Remote access is enabled and accessible to low-privileged users
  3. Review user privilege assignments
    Examine user accounts and their assigned privilege levels within the PowerProtect Data Manager user management system
    Affected if Low-privileged users have been assigned elevated or inappropriate permissions
  4. Inspect authorization boundaries
    Check application logs and audit records for operations that may have bypassed proper authorization checks
    Affected if Evidence shows operations were performed outside intended privilege boundaries

Environment is affected if PowerProtect Data Manager version is below 19.22 and low-privileged users have unauthorized elevated access or can achieve privilege escalation through the application

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 19.22 or later
Fixed in 19.22
Interim mitigation

Upgrade Dell PowerProtect Data Manager to version 19.22 or later to remediate this vulnerability. If immediate upgrading is not possible, restrict network access to trusted users and monitor for unauthorized privilege escalation attempts.

Recommended fix High confidence

PowerProtect Data Manager 19.22

  1. Identify the current version of PowerProtect Data Manager by checking the management interface or version command
  2. Schedule a maintenance window for the upgrade (downtime may be required)
  3. Perform a full backup of the current configuration and data according to Dell backup procedures
  4. Download PowerProtect Data Manager version 19.22 from Dell support website (support.dell.com)
  5. Follow Dell's documented upgrade procedure to apply version 19.22
  6. After upgrade, verify the new version is running by checking the version information
  7. Confirm the vulnerability is remediated by verifying the system security configuration
Caveat Review Dell upgrade documentation for any configuration changes or compatibility considerations before upgrading

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

Fix this in Powerprotect Data Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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