CVE-2026-5397
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 · uneditedIt has been identified that a vulnerability (CWE-427) exists in the UPS (Uninterruptible Power Supply) management application, whereby improper permissions on the installation directory allow a malicious actor to place a DLL that is then executed with administrator privileges. If a malicious DLL is placed in the installation directory of this product, there is a possibility that the malicious DLL may be executed by exploiting the product’s behavior of loading missing DLLs from the same directory as the executable during service startup.
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 confidenceA DLL hijacking vulnerability (CWE-427) exists in the UPS management application where improper permissions on the installation directory allow an attacker to plant a malicious DLL. When the service starts, it loads missing DLLs from the same directory as the executable, causing the malicious DLL to execute with administrator 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify UPS management application installationLocate the UPS management application on the system and determine its installed version. Common installation paths include C:\Program Files\, C:\Program Files (x86)\, or vendor-specific directories. Use system inventory tools or check Add/Remove Programs for UPS-related software.Affected if Application is present but version cannot be compared to a fixed patched version due to no CVE-specific CPE data - vulnerability exists in unpatched releases of affected UPS management software.
-
Verify installation directory permissionsRight-click the UPS management application installation folder, select Properties, then Security tab. Check which users and groups have Write or Modify permissions. Use command-line: icacls "<installation_path>" to enumerate permissions.Affected if Users other than Administrators or SYSTEM have Write or Modify permissions on the installation directory, allowing unauthorized DLL planting.
-
Check for unexpected DLL filesList all DLL files in the UPS management application installation directory. Compare against expected DLLs for that application. Use: dir "<installation_path>\*.dll"Affected if Unexpected or suspicious DLL files are present in the installation directory that do not belong to the application.
-
Identify related Windows serviceFind the Windows service associated with the UPS management application. Use Services.msc or: sc queryex type= service state= all | findstr /i "ups"Affected if A Windows service for the UPS management application runs with elevated privileges (LocalSystem, Local Service, or Administrator account).
The environment is affected if the UPS management application is installed with a weak permissions configuration that allows unprivileged users to write to the installation directory, combined with a service running with elevated privileges that could load a malicious DLL.
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 dataRestrict write permissions on the UPS management application installation directory to prevent unauthorized DLL planting. Additionally, implement secure DLL loading practices such as using full absolute paths, DLL search path elimination, or DLL signature verification.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5397 — 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-5397 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