dbcve.org
CWE-782Weakness · CWE-782

CVE-2026-8797

HIGH · 8.5 CVSS v4.0 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
An access control deficiency vulnerability exists in ExpressUpdate Agent for Windows. If a malicious user gains access to the product, arbitrary code could be executed with SYSTEM 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

ExpressUpdate Agent for Windows contains an access control deficiency that allows a user with access to the product to execute arbitrary code with SYSTEM privileges, effectively enabling local privilege escalation from a standard user account to the highest privilege level on Windows.

MitigationRestrict access to the ExpressUpdate Agent to trusted administrators only; apply vendor patches when available to implement proper authorization checks before code execution with elevated privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm ExpressUpdate Agent is installed
    Open Windows Services (services.msc) and look for a service named 'ExpressUpdate' or 'ExpressUpdate Agent', or check Program Files for an ExpressUpdate folder. Also check Add/Remove Programs for ExpressUpdate.
    Affected if The product is installed on the system
  2. Identify installed version
    Right-click the ExpressUpdate executable (typically in Program Files\ExpressUpdate or similar), select Properties, then check the Details tab for the File Version. Alternatively, run 'wmic product get name,version' or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ExpressUpdate.
    Affected if The installed version matches or predates any version with the vulnerability (no fixed version specified; compare to earliest known affected version if known)
  3. Check service configuration
    Open Services, right-click the ExpressUpdate service, select Properties. Note the 'Log on as' account. If it shows 'Local System' or 'NT AUTHORITY\SYSTEM', the service runs with SYSTEM privileges.
    Affected if The service runs as Local System or SYSTEM account
  4. Verify file/folder permissions
    Right-click the ExpressUpdate installation folder (typically Program Files\ExpressUpdate), go to Security tab. Check what permissions standard users have. Specifically, verify if Users or Non-Administrators have Write, Modify, or Execute permissions to the executable or configuration files.
    Affected if Standard (non-admin) users have Write, Modify, or Full Control permissions to ExpressUpdate executables or config files
  5. Test non-admin execution access
    As a standard (non-admin) user, attempt to run the ExpressUpdate executable or any updater component. Check if the process starts or if access is denied. Use 'icacls ExpressUpdate.exe' to list effective permissions.
    Affected if A standard user can launch or interact with ExpressUpdate components that execute with elevated privileges

A user is affected if ExpressUpdate Agent is installed AND the service runs with SYSTEM privileges AND standard users have sufficient permissions to trigger code execution through the product.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the ExpressUpdate Agent to trusted administrators only; apply vendor patches when available to implement proper authorization checks before code execution with elevated privileges.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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