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

CVE-2026-44609

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 EXE 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

Acronis DeviceLock DLP for Windows is vulnerable to local privilege escalation through EXE hijacking. The application loads executables from a path that allows an unprivileged attacker to inject a malicious executable, which then executes with elevated privileges when the legitimate process runs.

MitigationUpdate Acronis DeviceLock DLP to build 9.0.15051.93227 or later to address the EXE hijacking vulnerability. As a local privilege escalation, ensure the affected system is not exposed to untrusted local users.

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. Verify Acronis DeviceLock DLP is installed
    Open Windows Settings > Apps > Installed apps, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and search for 'DeviceLock' or 'Acronis DeviceLock DLP'
    Affected if Acronis DeviceLock DLP appears in the installed programs list
  2. Find the installed build version
    Open Control Panel > Programs and Features, right-click Acronis DeviceLock DLP and select Properties, or check the version in the application's About/Help menu
    Affected if The build number shown is lower than 9.0.15051.93227
  3. Check DLP installation directory permissions
    Right-click the DeviceLock installation folder (typically C:\Program Files\Acronis\DeviceLock or C:\Program Files (x86)\Acronis\DeviceLock), select Properties > Security, and verify that non-admin users lack Write or Modify permissions
    Affected if Users with low privileges have Write or Modify access to the DLP installation directory
  4. Inspect PATH environment variable directories
    Open System Properties > Environment Variables, select Path under User or System variables, and for each directory listed, verify that untrusted users cannot write executable files (right-click folder > Properties > Security)
    Affected if Any directory in the PATH that loads before the DLP binaries is writable by non-admin users, enabling EXE hijacking
  5. Identify DLP executable names vulnerable to hijacking
    Open Task Manager, go to Details tab, and look for DeviceLock-related processes such as DeviceLockService.exe, DLPAudit.exe, or DLPUpdate.exe; check the path column to locate where these executables load from
    Affected if The executable path points to a directory that appears before the legitimate DLP installation folder in the PATH, indicating potential hijacking

You are affected if Acronis DeviceLock DLP is installed with a build lower than 9.0.15051.93227 AND any directory in your PATH (or the DLP installation folder itself) is writable by untrusted users, allowing EXE hijacking to elevate privileges.

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 address the EXE hijacking vulnerability. As a local privilege escalation, ensure the affected system is not exposed to untrusted local users.

Recommended fix Moderate confidence

Acronis DeviceLock DLP build 9.0.15051.93227 or later

  1. Navigate to the official Acronis download portal or your licensed Acronis account
  2. Download Acronis DeviceLock DLP build 9.0.15051.93227 or the latest available build
  3. Verify the digital signature and hash of the installer before execution
  4. Ensure you have administrator privileges on the Windows system
  5. Close any running Acronis DeviceLock DLP services or related applications
  6. Run the installer and follow the on-screen prompts to upgrade the software
  7. After installation, verify the installed build version matches 9.0.15051.93227 or later via the product UI or Windows Programs and Features
  8. Restart the system if prompted to ensure all components load correctly
Caveat Review Acronis release notes for any changes to DLP policies or configuration requirements before upgrading in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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