dbcve.org
AgentApplication · Acronis

CVE-2025-11792

HIGH · 7.3 CVSS v3.0 Published 2026-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 DLL hijacking vulnerability. The following products are affected: Acronis Cyber Protect Cloud Agent (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 · moderate confidence

A DLL hijacking vulnerability in Acronis Cyber Protect Cloud Agent for Windows allows a local authenticated attacker to execute arbitrary code with elevated (SYSTEM) privileges by placing a malicious DLL in a location where the vulnerable application loads DLLs without proper path validation.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 41124 or later to incorporate the vendor patch for this vulnerability.

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

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. Confirm Acronis Agent is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Acronis*"}' in PowerShell. Look for 'Acronis Agent' or 'Acronis Cyber Protect Cloud Agent' in the installed programs list.
    Affected if Acronis Agent appears in the installed programs list
  2. Check installed Acronis Agent version
    In Programs and Features, click on Acronis Agent and look at the Version column, or run: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like "*Acronis*"}).DisplayVersion
    Affected if Version displayed is earlier than c25.10 (or build number is less than 41124)
  3. Check Acronis service status
    Open Services (services.msc) and look for 'Acronis Agent' service, or run: Get-Service | Where-Object {$_.Name -like "*Acronis*"}
    Affected if The Acronis Agent service is installed and running (the DLL hijacking only affects when the service loads vulnerable DLLs)
  4. Identify Acronis installation directory
    Run: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like "*Acronis*"}).InstallLocation. Typical path is C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\
    Affected if Acronis is installed in a directory where non-admin users can write to subfolders (required for DLL hijacking)

You are affected if Acronis Cyber Protect Cloud Agent is installed with a version earlier than c25.10 (or build lower than 41124) and the agent service is running.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Cyber Protect Cloud Agent to build 41124 or later to incorporate the vendor patch for this vulnerability.

Recommended fix High confidence

c25.10 (build 41124) or later

  1. Download Acronis Cyber Protect Cloud Agent version c25.10 (build 41124) or later from the Acronis management console or official download portal
  2. Stop the Acronis Agent Windows service
  3. Uninstall the current vulnerable version of the Acronis agent
  4. Install the updated agent package (c25.10 / build 41124 or later)
  5. Restart the computer or ensure the Acronis Agent service is running
  6. Verify the installed agent version is c25.10 or later by checking the agent properties in the management console

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

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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