CVE-2026-28712
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 Cyber Protect 17 (Windows) before build 41186.
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 confidenceA DLL hijacking vulnerability in Acronis Cyber Protect 17 on Windows allows a local authenticated attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the application loads DLLs without proper path validation.
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< 17.0.41186CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
-
Verify Acronis Cyber Protect 17 is installedOpen Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Acronis*"}' in PowerShellAffected if Acronis Cyber Protect 17 appears in installed programs list
-
Determine the installed build versionLaunch Acronis Cyber Protect and navigate to Help > About, or check the Windows registry under HKLM\SOFTWARE\Acronis\Global for the Build valueAffected if The build number displayed is less than 41186
-
Compare version against affected rangeIf you obtained the version from step 2, verify that it is below 17.0.41186Affected if Installed version is any build lower than 17.0.41186 (for example, 17.0.41100 or earlier)
-
Identify writable directories in Acronis installation pathRun 'icacls "C:\Program Files\Acronis"' in Command Prompt and check for 'BUILTIN\Users:(F)' or '(M)' permissions on subdirectoriesAffected if Standard users have write permissions to directories where Acronis loads DLLs at runtime
You are affected if Acronis Cyber Protect 17 is installed with a build version lower than 41186 AND standard users can write to directories from which the application loads DLLs.
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 · scoped17.0.41186
Upgrade Acronis Cyber Protect 17 to build 41186 or later to obtain the vendor patch. Alternatively, restrict write access to vulnerable directories and ensure the application uses secure DLL search paths.
Acronis Cyber Protect 17 build 41186 or later
- Locate the Acronis Cyber Protect 17 installer for build 41186 or later from your Acronis account or official download center
- Log in to the Windows system with administrator privileges
- Stop the Acronis Cyber Protect services if prompted during the upgrade process
- Run the installer and follow the on-screen prompts to upgrade to build 41186 or newer
- After installation completes, verify the build number in the product's About or Help section
- Restart the system if required to ensure all services load the updated binaries
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28712 — 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-28712 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