dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2022-46869

HIGH · 7.8 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 40278 or later.
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 during installation due to improper soft link handling. The following products are affected: Acronis Cyber Protect Home Office (Windows) before build 40278, Acronis True Image OEM (Windows) before build 42575.

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 Cyber Protect Home Office and Acronis True Image OEM Windows installers due to improper soft link (symlink) handling, allowing an attacker to gain elevated privileges during the installation process.

MitigationUpdate Acronis Cyber Protect Home Office to build 40278 or later, and Acronis True Image OEM to build 42575 or later.

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 Protect Home OfficeApplication
Affected:< 40278

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.1/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. Check if Acronis Cyber Protect Home Office is installed
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look for the product folder in C:\Program Files\Acronis\
    Affected if The product is found on the system
  2. Find the installed build version
    Check the registry value 'DisplayVersion' or 'Version' under the product's uninstall key, or right-click the main executable (e.g., cyber-protect.exe or true-image.exe) in Program Files and view Properties > Details
    Affected if A build/version number is returned
  3. Compare your build to the vulnerable range
    Parse the build number from the previous step and compare numerically to 40278. Note that some registry entries may show version numbers like 17.0.x rather than build numbers - check Acronis support or the product's about screen for the exact build number
    Affected if The installed build number is less than 40278
  4. Verify the installation component responsible for the vulnerability
    Locate the Windows installer (.msi or setup.exe) that was used for installation - the vulnerability exists in the installer itself, not just the installed application
    Affected if The installer version or build available on the system is older than 40278

You are affected if Acronis Cyber Protect Home Office is installed with a build number below 40278, as the installer contains the symlink vulnerability that could be exploited during repair/reinstall operations.

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 40278 or later
Fixed in 40278
Interim mitigation

Update Acronis Cyber Protect Home Office to build 40278 or later, and Acronis True Image OEM to build 42575 or later.

Recommended fix High confidence

Cyber Protect Home Office build 40278 or later; Acronis True Image OEM build 42575 or later

  1. 1. Identify the currently installed version of Acronis Cyber Protect Home Office or Acronis True Image OEM
  2. 2. If the installed build number is less than 40278 (for Cyber Protect Home Office) or less than 42575 (for Acronis True Image OEM), initiate an upgrade
  3. 3. Download the latest version from the official Acronis website or your organization's software distribution point
  4. 4. Uninstall the current vulnerable version following standard uninstallation procedures
  5. 5. Install the updated version with build 40278 or later (Cyber Protect Home Office) or build 42575 or later (Acronis True Image OEM)
  6. 6. Verify the installed build number matches or exceeds the fixed version
  7. 7. Restart the system if required by the installer

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

Fix this in Cyber Protect Home Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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