Cyber Resilience

CVE-2026-28264

LPE in Dell Powerprotect Data Manager ≤ 20.1.0.0

Published
08 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0013 3th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-28264 is a low-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Dell Powerprotect Data Manager. Its CVSS base score is 3.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Dell PowerProtect Agent Service, version(s) prior to 20.1, contain(s) an Incorrect Permission Assignment for Critical Resource vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Why these techniques?

Incorrect permissions on critical resource directly enable low-privileged local read access to sensitive data on the system.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-43885Same product: Dell Powerprotect Data Manager
CVE-2026-22267Same product: Dell Powerprotect Data Manager
CVE-2025-43888Same product: Dell Powerprotect Data Manager
CVE-2026-22269Same product: Dell Powerprotect Data Manager
CVE-2025-30480Same product: Dell Powerprotect Data Manager
CVE-2025-23375Same product: Dell Powerprotect Data Manager
CVE-2024-25971Same product: Dell Powerprotect Data Manager
CVE-2026-22268Same product: Dell Powerprotect Data Manager
CVE-2023-28062Same product: Dell Powerprotect Data Manager
CVE-2024-22454Same product: Dell Powerprotect Data Manager

Affected Assets

dell
powerprotect data manager
≤ 20.1.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-6 Least Privilege
  • AC-3 Access Enforcement
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly counters CWE-732 by requiring that only the minimum necessary permissions are granted to the Agent Service's critical resources, blocking low-privileged local access to exposed information.

prevent

Enforces the system's access-control policy on the affected resources so that an incorrect permission assignment cannot be exercised by an unauthorized local process or user.

prevent

Mandates applying and verifying secure configuration settings (including file/registry permissions) for the Agent Service, preventing the vulnerable default or mis-assigned rights from remaining in place.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires defining, enforcing, and reviewing access permissions and least privilege on resources.

PR.PS-01 mostly match
prevents

Hardened baselines and configuration management explicitly include correct permission settings for critical resources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.

prevents

Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.

prevents

Documented authorization, expiry rules, and audit logging of privileged accounts make it harder for critical resources to retain overly permissive or stale permission assignments.

prevents

Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.

prevents

Enforcing differentiated permissions on the source-code repository and program listings stops the assignment of overly broad default or inherited permissions to critical resources.

prevents

By defining and enforcing secure permission settings in configuration templates, the control reduces the likelihood that critical resources receive incorrect permission assignments.

References