dbcve.org
Device Management AgentApplication · Dell

CVE-2026-26949

HIGH · 7.8 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 26.02 or later.
See remediation →
80/100
Remediation priority · High
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 Device Management Agent (DDMA), versions prior to 26.02, contain an Incorrect Authorization vulnerability. A low privileged attacker with local 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 Device Management Agent (DDMA) versions prior to 26.02 contain an Incorrect Authorization vulnerability that allows a low-privileged local attacker to bypass proper authorization checks and elevate privileges to a higher permission level on the system.

MitigationUpgrade Dell Device Management Agent to version 26.02 or later to obtain the patched version with corrected authorization controls.

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
Device Management AgentApplication
Affected:< 26.02

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

CVSS:3.1/AV:L/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. Verify if Dell Device Management Agent is installed
    Check for DDMA installation in Program Files directories, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Dell Device Management Agent' or 'DDMA'
    Affected if No DDMA installation is found - the system is not affected because the vulnerable component is not present
  2. Retrieve the installed DDMA version number
    Use the Windows Registry key where DDMA is registered (typically under HKLM\SOFTWARE\Dell\DeviceManagementAgent or the Uninstall registry path), or run 'wmic product get name,version' if available, to obtain the exact installed version string
    Affected if The installed version string cannot be retrieved or is empty - version status is unknown
  3. Compare installed version against the vulnerable range
    Compare the retrieved version to 26.02 using standard version comparison (for example, 26.01.x, 26.00.x, 25.x.x would all be less than 26.02). Ensure the comparison treats 26.02 as a boundary where 26.02 and later are not vulnerable
    Affected if The installed version is lower than 26.02 (for example, 26.01, 25.10, 1.x) - the system is running a vulnerable version
  4. Confirm the DDMA service is present and executable
    Check if the DDMA service or scheduled task exists on the system using 'sc query DDMA' or by inspecting Windows Services for a Dell Device Management Agent service entry
    Affected if The DDMA service executable is present and installed - the vulnerability is exploitable if the version is vulnerable

A system is affected by CVE-2026-26949 if Dell Device Management Agent is installed with a version lower than 26.02 and the DDMA service or executable is present on the system.

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

Upgrade Dell Device Management Agent to version 26.02 or later to obtain the patched version with corrected authorization controls.

Recommended fix High confidence

26.02

  1. Navigate to Dell support website (www.dell.com) and search for Device Management Agent
  2. Locate the Dell Device Management Agent download page
  3. Download version 26.02 or later of the Dell Device Management Agent
  4. Backup current configuration if applicable
  5. Install the updated Device Management Agent version 26.02
  6. Verify the installation completed successfully
  7. Restart any dependent services if prompted

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

Fix this in Device Management Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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