CVE-2026-28264
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 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.
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 confidenceDell PowerProtect Agent Service versions prior to 20.1 have an Incorrect Permission Assignment vulnerability where low-privileged local users can access sensitive information due to improperly set permissions on critical resources. This is a local privilege escalation issue allowing information disclosure.
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< 20.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if PowerProtect Agent Service is installedOn Windows, check Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell. On Linux, run 'rpm -qa | grep -i powerprotect' or 'dpkg -l | grep -i powerprotect'.Affected if The product is installed and the version displayed is lower than 20.1 (e.g., 19.x, 18.x, etc.)
-
Determine PowerProtect Agent Service versionOn Windows, right-click the service in Services panel, select Properties, and note the 'File version' or check the executable in the installation directory. On Linux, run 'rpm -qi <package-name>' or check the version via the agent CLI if available.Affected if The reported version is prior to 20.1.0.0 or the version string starts with a number lower than 20.1
-
Check if PowerProtect Data Manager is installedOn Windows, review Programs and Features. On Linux, query installed packages: 'rpm -qa | grep -i data manager' or 'dpkg -l | grep -i data manager'.Affected if Dell PowerProtect Data Manager is present on the system and version is below 20.1.0.0
-
Verify PowerProtect Data Manager versionAccess the Data Manager web UI and navigate to About or Settings to view the version. Alternatively, check the installation directory for version files or run the product's CLI version command.Affected if The installed version is listed as anything less than 20.1.0.0 (such as 20.0.x, 19.x, or earlier)
-
Confirm vulnerable configuration existsReview file and directory permissions on the PowerProtect installation folder and configuration directories. Verify if low-privileged users have read or write access to sensitive folders (e.g., config, data, logs directories).Affected if Non-admin users or the 'Users' group have excessive permissions on critical PowerProtect directories or configuration files
The environment is affected if either Dell PowerProtect Agent Service version is below 20.1 or Dell PowerProtect Data Manager version is below 20.1.0.0, and the installation directories allow unauthorized access by low-privileged accounts.
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.
dbcve · scoped20.1.0.0
Upgrade Dell PowerProtect Agent Service to version 20.1 or later to obtain the corrected permission assignments. If immediate upgrade is not possible, verify and restrict file/folder permissions on the service directories to follow least-privilege principles.
20.1.0.0
- Identify current version of Dell PowerProtect Data Manager installed in the environment
- Review current backup and ensure all critical data is properly backed up before proceeding with upgrade
- Download Dell PowerProtect Data Manager version 20.1.0.0 or later from Dell support portal
- Execute the upgrade following Dell's standard upgrade procedures for PowerProtect Data Manager
- After upgrade completes, verify the installation was successful and the service is running
- Confirm the version has been updated to 20.1.0.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28264 — 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-28264 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