dbcve.org
Cyber ProtectApplication · Acronis

CVE-2026-28715

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 17.0.41186 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Sensitive information disclosure due to improper authorization checks. The following products are affected: Acronis Cyber Protect 17 (Linux, 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

Acronis Cyber Protect 17 contains an improper authorization vulnerability that allows authenticated users to access sensitive information they should not have access to. The issue stems from missing or insufficient authorization checks in certain API endpoints or functions, potentially exposing confidential data to unauthorized parties.

MitigationApply Acronis Cyber Protect 17 update to build 41186 or later. Verify all user roles and permissions align with least-privilege principles after patching.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify the installed Acronis Cyber Protect version
    Access the Acronis Cyber Protect management console or use the acrpsrv --version command-line tool to retrieve the exact build number
    Affected if The displayed version is below 17.0.41186
  2. Confirm the build number in the product interface
    Navigate to Help > About in the Cyber Protect console or check the installer details to verify the precise build version
    Affected if The build number is lower than 41186
  3. Review user role assignments
    In the management console, go to Settings > Users and Roles to list all assigned roles and permission levels for existing accounts
    Affected if Users with limited roles exist in the system (indicating the vulnerability could expose data they should not access)
  4. Audit API endpoint access controls
    Consult the Acronis Cyber Protect API documentation or examine server logs for requests to sensitive endpoints, noting which authenticated users successfully accessed them
    Affected if Lower-privilege users can successfully query endpoints that should require elevated permissions

The environment is affected if the installed Acronis Cyber Protect 17 build is below 41186, as the improper authorization flaw exists in those versions.

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

Apply Acronis Cyber Protect 17 update to build 41186 or later. Verify all user roles and permissions align with least-privilege principles after patching.

Recommended fix Moderate confidence

Acronis Cyber Protect 17 build 41186 or later

  1. 1. Backup current Acronis Cyber Protect configuration and any critical data
  2. 2. Download Acronis Cyber Protect 17 build 41186 or later from the official Acronis download center or your licensed portal
  3. 3. Review the Cyber Protect 17.0.41186 release notes for any specific upgrade requirements or known issues
  4. 4. Stop the Acronis Cyber Protect services on the affected machine before upgrading
  5. 5. Install the updated Cyber Protect 17.0.41186 (or latest available build) using the standard upgrade procedure for your platform (Windows installer or Linux package)
  6. 6. Verify the upgrade was successful by checking the build number in the Cyber Protect console or agent UI
  7. 7. Confirm the services have restarted properly and the agent is communicating with the management server
  8. 8. Validate that the authorization controls are functioning correctly and sensitive data is no longer accessible without proper authentication
Caveat Review release notes for potential compatibility issues with existing backup storage or third-party integrations before upgrading

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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