CVE-2026-26033
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 · uneditedUPS Multi-UPS Management Console (MUMC) version 01.06.0001 (A03) contains an Unquoted Search Path or Element (CWE-428) vulnerability, which allows a user with write access to a directory on the system drive to execute arbitrary code 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 · high confidenceThe UPS Multi-UPS Management Console (MUMC) version 01.06.0001 (A03) has an unquoted service path vulnerability (CWE-428). An attacker with write access to a directory in the service's executable path can place a malicious executable that will be launched with SYSTEM privileges when the service starts, due to Windows' path parsing behavior with unquoted paths containing spaces.
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= 01.06.0001_\(a03\)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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the UPS Multi-UPS Management Console serviceOpen Windows Services (services.msc) and look for a service related to 'UPS', 'Multi-UPS', 'MUMC', or 'Dell' with UPS in the name. Alternatively, run 'sc queryex type= service state= all' and search for these terms.Affected if The service exists in the environment.
-
Check the service executable pathRun 'sc qc <service_name>' to query the service configuration, then use 'wmic service where "name='<service_name>'" get PathName' to retrieve the full executable path.Affected if The reported path contains spaces and is not enclosed in quotation marks.
-
Verify the path contains unquoted spacesExamine the PathName output from the previous step. Look for paths that have spaces but are not wrapped in double quotes (e.g., C:\Program Files\Dell\... instead of "C:\Program Files\Dell\...").Affected if The executable path contains one or more spaces and lacks surrounding quotation marks.
-
Check write permissions on directories in the pathFor each directory in the unquoted path (e.g., C:\Program Files, C:\Program Files\Dell), right-click the folder in File Explorer, go to Properties > Security, and review the permissions. Alternatively, use 'icacls <directory_path>' to list users with write (W) or full control (F) permissions.Affected if Users other than Administrators or SYSTEM have write permissions to any directory in the service executable path.
Your environment is affected if the UPS Multi-UPS Management Console service is installed and its executable path contains unquoted spaces, allowing unauthorized users to potentially place malicious executables in directories along that path.
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.
From vendor dataIdentify the vulnerable service path in the Windows service configuration and update it to use fully quoted paths. Additionally, restrict write permissions on directories in the service executable path to prevent unauthorized file placement.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26033 — 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-26033 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