dbcve.org
Update Package FrameworkApplication · Dell

CVE-2026-23857

HIGH · 8.2 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 25.02.00 or later.
See remediation →
82/100
Remediation priority · High

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 Update Package (DUP) Framework, versions 23.12.00 through 24.12.00, contains an Improper Handling of Insufficient Permissions or Privileges 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 Update Package (DUP) Framework versions 23.12.00 through 24.12.00 contains an improper handling of insufficient permissions vulnerability. A low-privileged attacker with local system access can exploit this flaw to gain elevated privileges, potentially achieving administrator or SYSTEM-level access.

MitigationApply the vendor-provided patch or update to a version beyond 24.12.00 when available. Until then, restrict local user permissions and monitor for unauthorized privilege escalation attempts on affected systems.

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
Update Package FrameworkApplication
Affected:>= 23.12.00, < 25.02.00

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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. Check if Dell Update Package Framework is installed
    Look for Dell DUP Framework installation directories (typically under Program Files or Program Files x86) or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Dell Update Package' or 'DellUpdate'. You can also check for running processes related to Dell update services.
    Affected if Dell Update Package Framework is present on the system
  2. Identify the installed DUP Framework version
    Check the version of the installed Dell Update Package executable or DLL. Common locations include the installation directory (often C:\Program Files\Dell\UpdatePackage\ or similar). Right-click the main executable, select Properties, and view the Details tab for version information. Alternatively, query the Windows Registry for the DisplayVersion value under the Dell DUP uninstall key.
    Affected if The version displayed cannot be determined or is not visible
  3. Compare installed version against affected range
    The affected versions are 23.12.00 through 24.12.00 (specifically >= 23.12.00 and < 25.02.00). If your installed version is 23.12.00, 23.12.01, 24.x.x, or any version up to but not including 25.02.00, the system falls within the vulnerable range.
    Affected if Installed version is 23.12.00 or higher but lower than 25.02.00
  4. Check if DUP Framework service or scheduled task is active
    Open Services.msc and look for Dell Update Package related services. Also check Task Scheduler under Dell or UpdatePackage tasks. The vulnerability requires the DUP Framework to be running or scheduled to run, allowing a low-privileged user to trigger the privilege escalation.
    Affected if A Dell Update Package service or scheduled task is enabled and running on the system

If Dell Update Package Framework is installed with a version between 23.12.00 and 24.12.00 (inclusive) and the DUP service or scheduled task is active, the system is vulnerable to local privilege escalation.

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

Apply the vendor-provided patch or update to a version beyond 24.12.00 when available. Until then, restrict local user permissions and monitor for unauthorized privilege escalation attempts on affected systems.

Recommended fix Moderate confidence

Version 25.02.00 or later of Dell Update Package (DUP) Framework

  1. 1. Identify the current version of Dell Update Package (DUP) Framework installed on the system
  2. 2. Navigate to www.dell.com and locate the Dell Update Package Framework download page
  3. 3. Download version 25.02.00 or later from Dell's official support site
  4. 4. Verify the checksum of the downloaded package matches Dell's published checksum
  5. 5. Apply the update following Dell's standard update installation procedures
  6. 6. Verify the updated version is correctly installed post-upgrade

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

Fix this in Update Package Framework Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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