dbcve.org
True ImageApplication · Acronis

CVE-2026-27774

MEDIUM · 6.7 CVSS v3.0 Published 2026-04-02
Fix available
A fix is available. Upgrade to 2026 or later.
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 True Image (Windows) before build 42902.

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 · moderate confidence

DLL hijacking vulnerability in Acronis True Image for Windows allows local privilege escalation. An attacker can place a malicious DLL in a location where the application loads DLLs without proper path validation, potentially leading to arbitrary code execution with elevated privileges.

MitigationUpdate Acronis True Image to build 42902 or later. Prior to updating, ensure appropriate backup and testing procedures are in place.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
True ImageApplication
Affected:< 2026

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. Verify Acronis True Image installation
    Check if Acronis True Image for Windows is installed on the system by looking for the application in Program Files, Program Files (x86), or checking the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an Acronis True Image entry.
    Affected if The application is not installed, this CVE does not apply.
  2. Identify the installed build number
    Open Acronis True Image and navigate to Help > About, or check the Windows registry under HKLM\SOFTWARE\Acronis\TrueImage\Setup\Information for a BuildNumber value, or look at the file version of the main executable (typically TrueImage.exe in the installation directory.
    Affected if Unable to determine the build number.
  3. Compare build against affected range
    Compare the installed build number to the affected threshold of 42902. Versions before build 42902 are vulnerable.
    Affected if The installed build number is less than 42902.
  4. Assess privilege context
    Observe whether Acronis True Image runs with elevated privileges or requests UAC elevation during normal operation, since the DLL hijacking only leads to privilege escalation when the application loads the malicious DLL with elevated rights.
    Affected if The application runs with elevated privileges and an older vulnerable build is installed.

If Acronis True Image for Windows is installed with a build number lower than 42902, the environment is affected by this DLL hijacking vulnerability.

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
Upgrade available Upgrade to 2026 or later
Fixed in 2026
Interim mitigation

Update Acronis True Image to build 42902 or later. Prior to updating, ensure appropriate backup and testing procedures are in place.

Recommended fix Moderate confidence

True Image 2026 (build 42902 or later)

  1. 1. Ensure you have a backup of your current Acronis True Image installation and important data
  2. 2. Navigate to the official Acronis download page or use the built-in update mechanism within Acronis True Image
  3. 3. Download True Image version 2026 (build 42902 or later) for Windows
  4. 4. Uninstall the current (vulnerable) version of Acronis True Image through Windows Control Panel > Programs and Features
  5. 5. Restart your computer to ensure all previous processes are terminated
  6. 6. Install the downloaded True Image 2026 (build 42902 or later)
  7. 7. Verify the installation by checking Help > About in the application, confirming the build number is 42902 or higher
  8. 8. Ensure the software runs without errors and all functionality is working as expected
Caveat Review Acronis release notes for 2026 version to check for any new system requirements or feature changes compared to your current version

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

Fix this in True Image Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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