dbcve.org
Cyber ProtectApplication · Acronis

CVE-2026-28722

HIGH · 7.3 CVSS v3.0 Published 2026-03-06
Fix available
A fix is available. Upgrade to 17.0.41186 or later.
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 improper soft link handling. 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 · high confidence

Local privilege escalation vulnerability in Acronis Cyber Protect 17 (Windows) versions before build 41186 due to improper symbolic/soft link handling. A local attacker with low-privilege access can exploit improper validation of symbolic links to gain elevated privileges on the affected system.

MitigationUpgrade Acronis Cyber Protect 17 to build 41186 or later, or apply the vendor-provided security patch. Verify the upgrade in a non-production environment before deploying organization-wide.

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
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. Verify Acronis Cyber Protect 17 installation
    Open Windows Control Panel or Settings > Apps & Features, locate 'Acronis Cyber Protect', and note the displayed version and build number. Alternatively, open an elevated command prompt and run: wmic product get name,version
    Affected if Acronis Cyber Protect 17 is installed with a build version lower than 41186
  2. Check Acronis service status
    Open Services.msc or run 'sc query acronis' in command prompt to verify if the Acronis Cyber Protect service is currently running
    Affected if The Acronis service is running and accessible to low-privilege local users
  3. Verify user access to Acronis program directory
    Navigate to the Acronis installation directory (commonly C:\Program Files\Acronis or C:\Program Files (x86)\Acronis), right-click the folder, select Properties > Security, and review which users have Read or Write permissions
    Affected if Low-privilege users have write access to Acronis directories containing executable or configuration files
  4. Check for symbolic link creation capability
    Review Acronis service configuration and file permissions to determine if unprivileged users can create or manipulate symbolic links within Acronis-managed paths. Use 'icacls' command on relevant directories to inspect ACLs
    Affected if Unprivileged users can create symbolic links in directories used by Acronis services

You are affected if Acronis Cyber Protect 17 for Windows is installed with a build number below 41186 and low-privilege users can interact with the running service or its directories.

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

Upgrade Acronis Cyber Protect 17 to build 41186 or later, or apply the vendor-provided security patch. Verify the upgrade in a non-production environment before deploying organization-wide.

Recommended fix Moderate confidence

Acronis Cyber Protect 17 build 41186 or later

  1. Upgrade Acronis Cyber Protect 17 (Windows) to build 41186 or later to remediate the local privilege escalation vulnerability caused by improper soft link handling (CWE-610).
  2. Verify the upgrade was successful by checking the product build version in the Acronis Cyber Protect console or about information.
  3. Test that normal Cyber Protect operations function correctly after the upgrade.

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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