dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2026-50033

HIGH · 7.3 CVSS v3.0 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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
Local privilege escalation due to DLL hijacking vulnerability. The following products are affected: Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227.

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 confidence

A DLL hijacking vulnerability in Acronis DeviceLock DLP on Windows allows local users to elevate privileges by placing a malicious DLL in a location where the application loads DLLs from an unsecured path. The vulnerability exists in versions before build 9.0.15051.93227.

MitigationUpdate Acronis DeviceLock DLP to build 9.0.15051.93227 or later to incorporate the vendor fix for the DLL hijacking vulnerability.

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
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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. Identify if Acronis DeviceLock DLP is installed
    Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for entries containing 'DeviceLock' or look for the application folder in Program Files (typically C:\Program Files\Acronis\DeviceLock or similar)
    Affected if Acronis DeviceLock DLP is present on the system
  2. Determine the installed build version
    Locate the DeviceLock executable (often DeviceLock.exe or DLService.exe) in the installation directory, right-click and view Properties, or query the registry key HKLM\SOFTWARE\Acronis\DeviceLock\Version for the build number
    Affected if The build version returned is lower than 9.0.15051.93227
  3. Verify the vulnerable DLL loading behavior
    Review the application installation directory for missing or writable DLL files, or use Process Monitor (sysinternals) to observe DLL load paths when the Acronis DeviceLock service starts
    Affected if The application loads DLLs from directories with weak permissions or the application directory contains world-writable DLLs
  4. Check for weak folder permissions on the application directory
    Right-click the Acronis DeviceLock installation folder, go to Properties > Security, and verify which users have Write or Modify permissions beyond Administrators and SYSTEM
    Affected if Non-admin users have Write or Modify permissions to directories from which the application loads DLLs

The system is affected if Acronis DeviceLock DLP is installed with a build version lower than 9.0.15051.93227 and the application directory or DLL load paths have weak permissions allowing unprivileged users to place malicious DLLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Acronis DeviceLock DLP to build 9.0.15051.93227 or later to incorporate the vendor fix for the DLL hijacking vulnerability.

Recommended fix High confidence

Acronis DeviceLock DLP build 9.0.15051.93227 or later

  1. Backup any critical data on the system before proceeding with the upgrade
  2. Navigate to the official Acronis support portal or download center at https://www.acronis.com/support/
  3. Search for Acronis DeviceLock DLP and locate the version with build 9.0.15051.93227 or later
  4. Download the installer for the fixed build
  5. Close any running instances of Acronis DeviceLock DLP
  6. Run the installer with administrative privileges
  7. Follow the on-screen installation wizard to complete the upgrade
  8. Restart the system if prompted by the installer

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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