CVE-2026-28728
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 · uneditedLocal 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 confidenceAcronis True Image for Windows versions prior to build 42902 are vulnerable to DLL hijacking, allowing a local attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the application loads DLLs from an unsecured path.
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< 2026CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Acronis True Image versionOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\TrueImage\CurrentVersion, or right-click the installed application shortcut and select Properties to view the file versionAffected if The displayed version or build number is below 2026 (or build number is below 42902)
-
Confirm the application is installedCheck for the presence of Acronis True Image in Program Files or Program Files (x86) directory, typically under C:\Program Files\Acronis\TrueImageAffected if The application directory exists and contains the True Image executable
-
Verify application execution pathLaunch Acronis True Image and observe that it runs with elevated privileges (Task Manager shows NT AUTHORITY\SYSTEM under User name for the process)Affected if The process runs as SYSTEM or another elevated account while a low-privilege user can trigger its execution
-
Check for user-writable directories in application pathExamine the Acronis True Image installation directory and its subdirectories for permissions allowing standard users to write files (use icacls command or right-click Properties > Security)Affected if Any directory in the application path is writable by non-admin users, allowing DLL injection
You are affected if Acronis True Image is installed with a version or build number below 42902 (or any version before 2026) and the installation directory or related paths are writable by low-privilege users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026
Update Acronis True Image to build 42902 or later. Alternatively, ensure strict control over directory permissions to prevent unauthorized DLL placement in application directories.
Acronis True Image build 42902 or later
- 1. Open Acronis True Image application
- 2. Navigate to Help > About or check the current build number
- 3. If the build number is below 42902, download the latest version from the official Acronis website or use the built-in update mechanism
- 4. Run the installer and complete the upgrade process
- 5. Restart the application and verify the build number is 42902 or higher
- 6. Confirm the DLL hijacking vulnerability is resolved by ensuring the application loads DLLs from secure locations only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-28728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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