dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-9578

HIGH · 7.8 CVSS v3.0 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Local privilege escalation due to insecure folder permissions. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 40734.

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 Cloud Agent for Windows versions before build 40734 contain insecure folder permissions that allow a local attacker to manipulate files or gain elevated privileges. This is a local privilege escalation vulnerability where improper permission assignments on agent directories permit unauthorized access.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 40734 or later to remediate the insecure folder permissions vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 Cloud Agent is installed
    Look for the Acronis installation directory at C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\, or query the Windows Registry under HKLM\SOFTWARE\Acronis\ for installed components
    Affected if The agent directory or registry keys exist, indicating the product is present on the system
  2. Determine the installed build version
    Open the Acronis installation folder and locate a version information file (commonly version.info, version.txt, or a similar file) and read the build number, or query the registry key HKLM\SOFTWARE\Acronis\ for a Build or Version value
    Affected if The build version number is lower than 40734, meaning the version is vulnerable
  3. Identify the agent installation directory path
    In the Acronis installation folder, identify subdirectories such as \Agent, \Bin, or any directory containing executable files related to the protection agent
    Affected if The agent subdirectories exist, which are the directories whose permissions must be checked
  4. Examine folder permissions on agent directories
    Open Command Prompt or PowerShell and run icacls "C:\Program Files\Acronis\*" or target specific agent subdirectories to list all granted permissions, looking for entries that grant Write, Modify, or Full Control to standard users, the Users group, or Everyone
    Affected if Non-administrative users or groups such as Users or Everyone have Write, Modify, or Full Control permissions on agent directories, indicating the insecure permission vulnerability is present

The environment is affected if Acronis Cyber Protect Cloud Agent for Windows is installed with a build version earlier than 40734 and the agent directories have overly permissive access control entries that allow non-admin users to modify files.

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 40734 or later to remediate the insecure folder permissions vulnerability.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent (Windows) build 40734 or later

  1. Identify all Windows systems with Acronis Cyber Protect Cloud Agent installed
  2. Check the current build version of the agent on each system (typically via the agent's UI or system information)
  3. For systems running builds before 40734, download the updated agent installer from Acronis official download channels or your Acronis management console
  4. Schedule a maintenance window for the update process
  5. Run the updated installer to upgrade the agent to build 40734 or later
  6. Verify the upgrade was successful by confirming the new build number (40734 or higher)
  7. Confirm the agent is communicating properly with the management console
  8. Test that backup and protection functionality is operating normally

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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