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

CVE-2025-11178

HIGH · 7.3 CVSS v3.0 Published 2025-09-30
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 True Image (Windows) before build 42386, Acronis True Image for Western Digital (Windows) before build 42636, Acronis True Image for SanDisk (Windows) before build 42679, Acronis True Image OEM (Windows) before build 42575.

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

Local privilege escalation via DLL hijacking in Acronis True Image for Windows. The vulnerability allows an attacker to place a malicious DLL in a location where the application loads DLLs from, potentially executing code with elevated privileges.

MitigationUpgrade Acronis True Image to the fixed build numbers (42386, 42636, 42679, or 42575 depending on the specific product variant).

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. Locate Acronis True Image installation
    Search for the Acronis True Image installation directory, typically in C:\Program Files\Acronis\True Image or C:\Program Files (x86)\Acronis\True Image, or search for TrueImage.exe using Get-ChildItem -Recurse
    Affected if Acronis True Image is installed on the system
  2. Determine installed version
    Right-click TrueImage.exe, select Properties, and check the File Version field, or run: (Get-Item 'C:\Program Files\Acronis\True Image\TrueImage.exe').VersionInfo.FileVersion
    Affected if Version cannot be determined or version number is lower than fixed builds
  3. Compare version to fixed builds
    Compare the discovered version/build number against the fixed builds: 42386, 42636, 42679, or 42575 (depending on your specific product variant). Any version below these is vulnerable.
    Affected if Installed build number is lower than 42386, 42636, 42679, or 42575 (whichever applies to the detected variant)
  4. Identify writable DLL directories
    Check permissions on the Acronis installation directory and subdirectories to determine if standard users can write files to locations where the application loads DLLs from
    Affected if Standard users have write access to directories in the application's DLL search path

A system is affected if Acronis True Image for Windows is installed with a version below the fixed build numbers and the application loads DLLs from writable directories accessible to unprivileged 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

Upgrade Acronis True Image to the fixed build numbers (42386, 42636, 42679, or 42575 depending on the specific product variant).

Recommended fix High confidence

Acronis True Image (Windows) build 42386+, True Image for Western Digital build 42636+, True Image for SanDisk build 42679+, True Image OEM build 42575+

  1. Identify the specific Acronis True Image product installed (True Image, True Image for Western Digital, True Image for SanDisk, or True Image OEM)
  2. Check the current build version in the application (usually in Help > About or Settings > About)
  3. For Acronis True Image: upgrade to build 42386 or later
  4. For Acronis True Image for Western Digital: upgrade to build 42636 or later
  5. For Acronis True Image for SanDisk: upgrade to build 42679 or later
  6. For Acronis True Image OEM: upgrade to build 42575 or later
  7. Download the updated version from the official Acronis website or trusted OEM channel
  8. Install the update following standard Acronis installation procedures

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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