dbcve.org
Powerprotect Data ManagerApplication · Dell

CVE-2026-22266

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 Improper Verification of Source of a Communication Channel vulnerability in the REST API. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to protection mechanism bypass.

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 improper verification of source of communication channel vulnerability in the REST API. This allows a high-privileged attacker to bypass protection mechanisms by exploiting insufficient validation of the origin of API requests. The vulnerability enables attackers with remote access and valid high-privilege credentials to circumvent security controls intended to verify request authenticity.

MitigationUpgrade Dell PowerProtect Data Manager to version 19.22 or later to obtain the vendor patch addressing this improper source verification vulnerability in the REST API.

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 installed PowerProtect Data Manager version
    Access the PowerProtect Data Manager admin console or use the management CLI to retrieve the current software version. This is typically found in the system information or about section of the management interface.
    Affected if The installed version is any release prior to 19.22 (for example, 19.21, 19.20, earlier releases). Versions 19.22 and later contain the fix.
  2. Confirm REST API interface is accessible
    Verify that the PowerProtect Data Manager REST API endpoint is exposed and reachable on the network. Check network configuration or firewall rules to confirm external or internal systems can submit API requests to the manager.
    Affected if The REST API is enabled and accessible from any network location where potential attackers could reach it.
  3. Review API access control configuration
    Examine the PowerProtect Data Manager security settings related to API request validation. Look for configuration options that control source/origin verification for REST API communications.
    Affected if Source verification is disabled, set to weak validation, or allows bypass of origin checks for authenticated API requests.
  4. Audit high-privilege account activity
    Review authentication and API access logs for any high-privilege accounts. Look for anomalous API calls, especially those originating from unexpected IP addresses or showing signs of credential reuse.
    Affected if High-privilege API activity shows requests originating from IPs outside expected ranges or patterns inconsistent with legitimate administrator behavior.

You are affected if your PowerProtect Data Manager version is earlier than 19.22 and the REST API is accessible, since the vulnerability allows high-privileged attackers to bypass source verification in API requests.

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 obtain the vendor patch addressing this improper source verification vulnerability in the REST API.

Recommended fix Moderate confidence

19.22

  1. 1. Identify the current version of Dell PowerProtect Data Manager installed in the environment
  2. 2. Review the Dell PowerProtect Data Manager 19.22 release notes for upgrade prerequisites and changes
  3. 3. Create a complete backup of the current configuration and verify recoverability
  4. 4. Schedule a maintenance window appropriate for the upgrade
  5. 5. Follow Dell's official upgrade procedure for PowerProtect Data Manager to update to version 19.22
  6. 6. After upgrade, verify the REST API vulnerability is resolved by confirming the version shows 19.22 or later
  7. 7. Validate that core Data Manager functions (backup, restore, protection policies) operate correctly post-upgrade

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Check whether your project pulls in CVE-2026-22266 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-22266 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