dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-0705

MEDIUM · 6.7 CVSS v3.0 Published 2026-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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 insecure folder permissions. The following products are affected: Acronis Cloud Manager (Windows) before build 6.4.25342.354.

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

Local privilege escalation vulnerability in Acronis Cloud Manager for Windows caused by insecure folder permissions. Low-privileged local users can modify executable locations or configuration files in improperly secured directories to gain elevated privileges.

MitigationAudit and restrict folder permissions on the Acronis Cloud Manager installation directory to prevent write access by non-privileged users; upgrade to build 6.4.25342.354 or later which contains the security fix.

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

CVSS:3.0/AV:L/AC:H/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. Identify Acronis Cloud Manager installation path
    Check for the presence of Acronis Cloud Manager in standard installation locations such as C:\Program Files\Acronis\CloudManager or C:\Program Files (x86)\Acronis\CloudManager, or look for the service via Windows Services (services.msc) and check the executable path.
    Affected if Acronis Cloud Manager is installed on the system.
  2. Determine installed version or build number
    Right-click the Acronis Cloud Manager executable (typically cloudmanager.exe or acroniscloudmanager.exe) in the installation folder, select Properties, and view the Details tab for the Product Version or File Version. Alternatively, open Windows Services, locate the Acronis Cloud Manager service, check its properties, or use the command: dir "<installation_path>\*.exe" /s to list executables with version info.
    Affected if The installed version or build number is below 6.4.25342.354.
  3. Audit folder permissions on the installation directory
    Right-click the Acronis Cloud Manager installation folder, select Properties, go to the Security tab, and review the permissions for Users or other non-privileged groups. Specifically check if Write or Modify permissions are granted to standard users or the Users group.
    Affected if Non-privileged users or the Users group have Write or Modify permissions on the Acronis Cloud Manager installation directory or its subdirectories.
  4. Inspect executable locations for world-writable folders
    Navigate to the installation folder and subfolders (including bin, config, or any directories containing executable files). Right-click each folder, check Properties > Security, and verify that only Administrators and SYSTEM have write access.
    Affected if Any folder containing executables or configuration files within the Acronis Cloud Manager directory is writable by low-privileged users.
  5. Verify configuration file integrity
    Locate configuration files (commonly .xml, .ini, or .config files) in the Acronis Cloud Manager installation directory. Check their permissions to confirm only Administrators can modify them.
    Affected if Configuration files in the installation directory are modifiable by non-administrative users.

The system is affected if Acronis Cloud Manager is installed with a build number below 6.4.25342.354 and the installation directory or its contents are writable by non-privileged users.

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

Audit and restrict folder permissions on the Acronis Cloud Manager installation directory to prevent write access by non-privileged users; upgrade to build 6.4.25342.354 or later which contains the security fix.

Recommended fix High confidence

Build 6.4.25342.354 or later of Acronis Cloud Manager (Windows)

  1. 1. Identify the current version of Acronis Cloud Manager installed on the Windows system
  2. 2. Navigate to the official Acronis download center or contact Acronis support to obtain build 6.4.25342.354 or a later stable release
  3. 3. Create a full backup of the Acronis Cloud Manager configuration and any critical data
  4. 4. Stop the Acronis Cloud Manager service to ensure a clean upgrade process
  5. 5. Run the installer for the updated build (6.4.25342.354 or later) with administrative privileges
  6. 6. Follow the on-screen installation wizard to complete the upgrade
  7. 7. After installation, verify that folder permissions have been corrected and are no longer overly permissive
  8. 8. Restart the Acronis Cloud Manager service and confirm the application functions 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-2026-0705 — 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-0705 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