dbcve.org
AgentApplication · Acronis

CVE-2025-11791

HIGH · 7.1 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 17.0.41186 or later.
See remediation →
73/100
Remediation priority · Elevated
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 and manipulation due to insufficient authorization checks. The following products are affected: Acronis Cyber Protect 17 (Linux, macOS, Windows) before build 41186, Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 41124.

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

This is an authorization bypass vulnerability where insufficient access control checks allow authenticated users to disclose sensitive information and manipulate data they should not have access to. The flaw affects both Acronis Cyber Protect 17 and Cyber Protect Cloud Agent across Linux, macOS, and Windows platforms.

MitigationUpgrade to Acronis Cyber Protect 17 build 41186 or later, and Cyber Protect Cloud Agent build 41124 or later. Prioritize systems handling sensitive data given the combined disclosure and manipulation impact.

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
AgentApplication
Affected:< c25.10
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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/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 checks

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

  1. Check Acronis Cyber Protect 17 version on Windows
    Open Windows Registry Editor and navigate to HKLM\SOFTWARE\Acronis\MMS\, or open Control Panel > Programs and Features and look for 'Acronis Cyber Protect 17' to see the installed version and build number
    Affected if The displayed version is earlier than 17.0.41186 or the build number is lower than 41186
  2. Check Acronis Cyber Protect Cloud Agent version on Windows
    Open Windows Registry Editor and navigate to HKLM\SOFTWARE\Acronis\MMS\, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Acronis*"}' in PowerShell to list installed Acronis components and their versions
    Affected if The agent version shows c25.x with build earlier than 41124, or any version before c25.10
  3. Check Acronis agent version on Linux
    Run 'rpm -qa | grep -i acronis' or 'dpkg -l | grep -i acronis' depending on the package manager to list installed Acronis packages, or check /var/lib/Acronis/ for installation info
    Affected if The installed package version is earlier than c25.10 or the build is lower than 41124
  4. Check Acronis agent version on macOS
    Run 'pkgutil --pkg-info=com.acronis.*' or check /Library/Acronis/ for installation files and version information
    Affected if The package version is earlier than c25.10 or shows a build number below 41124
  5. Verify access control configuration
    Review the Acronis management console or registry settings under HKLM\SOFTWARE\Acronis\MMS\ for any custom access control configurations, and audit user permissions within the Acronis management interface
    Affected if Non-administrative user accounts have been granted elevated privileges or there are custom permission rules that may bypass standard authorization checks

You are affected if any Acronis Cyber Protect 17 installation is earlier than build 41186, or any Acronis Cloud Agent is earlier than build c25.10 (41124) on any platform.

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 to Acronis Cyber Protect 17 build 41186 or later, and Cyber Protect Cloud Agent build 41124 or later. Prioritize systems handling sensitive data given the combined disclosure and manipulation impact.

Recommended fix High confidence

Acronis Cyber Protect 17 build 41186 or later; Acronis Cyber Protect Cloud Agent c25.10 (build 41124) or later

  1. 1. Identify the currently installed Acronis Cyber Protect or Agent version and build number
  2. 2. For Acronis Cyber Protect 17: Upgrade to build 41186 or later for all platforms (Linux, macOS, Windows)
  3. 3. For Acronis Cyber Protect Cloud Agent: Upgrade to build 41124 (c25.10) or later for all platforms (Linux, macOS, Windows)
  4. 4. Verify the upgrade was successful by confirming the new build number in the product UI or via command line
  5. 5. Test that sensitive operations now require proper authorization

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

Fix this in Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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