dbcve.org
Cyber ProtectApplication · Acronis

CVE-2026-28717

MEDIUM · 5.0 CVSS v3.0 Published 2026-03-06
Fix available
A fix is available. Upgrade to 17.0.41186 or later.
See remediation →
50/100
Remediation priority · Moderate

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 improper directory permissions. 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 confidence

Local privilege escalation vulnerability in Acronis Cyber Protect 17 (Windows) caused by improper directory permissions, allowing a local authenticated user to potentially gain elevated privileges by exploiting misconfigured access controls on specific directories.

MitigationUpdate Acronis Cyber Protect 17 to build 41186 or later, which contains the fix for the improper directory permissions. Alternatively, review and restrict directory permissions according to the principle of least privilege until the patch can be applied.

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
Cyber ProtectApplication
Affected:< 17.0.41186

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
None
Integrity
High
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Acronis Cyber Protect 17 installation
    Open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software
    Affected if Acronis Cyber Protect 17 appears in the installed programs list
  2. Check installed version number
    Locate the Acronis Cyber Protect version in the program properties or run 'Get-ItemProperty "C:\Program Files\Acronis\Cyber Protect\version.ini"' if it exists to read the build number
    Affected if The version or build number is lower than 17.0.41186
  3. Inspect directory permissions on Acronis installation folder
    Right-click the Acronis installation directory (typically C:\Program Files\Acronis or C:\ProgramData\Acronis), select Properties, then Security tab. Check which users and groups have permissions and what level of access they have
    Affected if Authenticated users or non-admin users have write or modify permissions to directories that should be restricted to administrators only
  4. Verify if low-privilege user can modify protected directories
    Using a standard user account (not administrator), attempt to create or modify a file in suspected directories like C:\Program Files\Acronis\ or C:\ProgramData\Acronis\
    Affected if A standard authenticated user can successfully write or modify files in directories that should be admin-only

If Acronis Cyber Protect 17 is installed with a version below 17.0.41186 AND directory permissions allow authenticated users write access to protected directories, the environment is affected by this privilege escalation 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 17.0.41186 or later
Fixed in 17.0.41186
Interim mitigation

Update Acronis Cyber Protect 17 to build 41186 or later, which contains the fix for the improper directory permissions. Alternatively, review and restrict directory permissions according to the principle of least privilege until the patch can be applied.

Recommended fix High confidence

Acronis Cyber Protect 17 build 41186 or later

  1. 1. Identify the current installed build version of Acronis Cyber Protect 17 on the Windows system
  2. 2. Upgrade Acronis Cyber Protect 17 to build 41186 or later, which contains the security fix for the improper directory permissions vulnerability
  3. 3. After upgrade, verify the new build version is correctly installed
  4. 4. Confirm the directory permissions have been corrected by reviewing the Acronis installation directories

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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