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

CVE-2026-25852

MEDIUM · 6.7 CVSS v3.0 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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.93212.

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

This is a DLL hijacking vulnerability in Acronis DeviceLock DLP for Windows that allows a local attacker to escalate privileges. The application likely loads DLLs without using fully qualified paths, enabling an attacker to place a malicious DLL in a location that gets loaded by the vulnerable application, potentially executing code with elevated privileges.

MitigationUpdate Acronis DeviceLock DLP to build 9.0.93212 or later. If patching is not immediately possible, restrict write access to directories in the application DLL search path to prevent placement of malicious DLLs.

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

CVSS:3.0/AV:L/AC:H/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. Confirm Acronis DeviceLock DLP is installed
    Check for the presence of Acronis DeviceLock DLP in the Windows Programs and Features list, or look for its installation directory under C:\Program Files\Acronis\DeviceLock or C:\Program Files (x86)\Acronis\DeviceLock
    Affected if The application is installed on the system
  2. Locate the installed version information
    Open Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product GUID} or look for version info in the main executable properties (right-click DeviceLock.exe and select Properties > Details)
    Affected if Unable to locate version data means the application may not be properly installed
  3. Extract the build number
    In the version details, identify the Build number field - this is the specific version identifier needed for comparison (format is typically x.x.xxxxx)
    Affected if Build number is missing or cannot be determined from the executable properties
  4. Compare against the fixed version
    Compare the installed build number to the fixed version 9.0.93212 - any version lower than this build is vulnerable
    Affected if Installed build is less than 9.0.93212 (for example, 9.0.93100 or earlier)
  5. Identify DLL search path directories
    Use Process Monitor (from Sysinternals) to capture DLL loading activity when DeviceLock.exe starts, filtering for DLL names and paths that are not fully qualified
    Affected if DeviceLock.exe loads DLLs from directories writable by lower-privileged users without using fully qualified paths

The system is affected if Acronis DeviceLock DLP is installed with a build number lower than 9.0.93212 and the application loads DLLs from directories accessible to non-privileged users.

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.93212 or later. If patching is not immediately possible, restrict write access to directories in the application DLL search path to prevent placement of malicious DLLs.

Recommended fix High confidence

Acronis DeviceLock DLP build 9.0.93212 or later

  1. Identify the currently installed Acronis DeviceLock DLP version (e.g., open the software, check About or use 'Add/Remove Programs').
  2. Navigate to the official Acronis support portal or contact Acronis Customer Support to obtain the latest installer for DeviceLock DLP.
  3. Verify the installer file is digitally signed by Acronis and matches the hash provided by the vendor.
  4. Backup the current DeviceLock DLP configuration (export settings if the UI provides an export function).
  5. Run the installer and follow the on-screen instructions to upgrade to build 9.0.93212 or later.
  6. After installation, confirm the new build number matches the fixed version (e.g., 9.0.93212).
  7. Restart the Windows host to ensure all DeviceLock services load the updated DLLs.
  8. Validate that the software functions correctly and that the DLL search path is now controlled (no untrusted directories in the system PATH that precede the program directory).
Caveat Minimal; backup configuration before upgrade recommended

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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