CVE-2024-8766
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 · uneditedLocal privilege escalation due to DLL hijacking vulnerability. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 38235, Acronis Cyber Protect 16 (Windows) before build 39169.
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 confidenceA local privilege escalation vulnerability exists in Acronis Cyber Protect Cloud Agent and Acronis Cyber Protect 16 for Windows due to DLL hijacking. The vulnerability allows a local attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the affected application loads libraries from. The vulnerability affects specific builds prior to 38235 for the Cloud Agent and 39169 for Cyber Protect 16.
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Acronis Cyber Protect Cloud Agent is installedOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or use PowerShell: Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Acronis*Cyber*Protect*Cloud*Agent*'} | Select-Object DisplayName, DisplayVersionAffected if The product is installed with a build version lower than 38235
-
Check if Acronis Cyber Protect 16 is installedOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or use PowerShell: Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Acronis*Cyber*Protect*16*'} | Select-Object DisplayName, DisplayVersionAffected if The product is installed with a build version lower than 39169
-
Verify the exact build number via Acronis service informationOpen Services panel (services.msc), locate the Acronis service, right-click and select Properties, or check the version information in the Acronis installation directory typically found under C:\Program Files\Acronis\Affected if The build number displayed is prior to 38235 for Cloud Agent or prior to 39169 for Cyber Protect 16
If either Acronis Cyber Protect Cloud Agent (build < 38235) or Acronis Cyber Protect 16 (build < 39169) is installed and running on the system, the environment is vulnerable to DLL hijacking privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Acronis Cyber Protect Cloud Agent to build 38235 or higher, and Acronis Cyber Protect 16 to build 39169 or higher. Organizations should verify current installed versions and apply the appropriate updates.
Acronis Cyber Protect Cloud Agent: build 38235 or later; Acronis Cyber Protect 16: build 39169 or later
- Identify which Acronis product is installed: Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 16
- For Acronis Cyber Protect Cloud Agent (Windows): upgrade to build 38235 or later
- For Acronis Cyber Protect 16 (Windows): upgrade to build 39169 or later
- Download the updated agent from the Acronis management console or official Acronis download center
- Install the updated build on all affected Windows machines
- Verify the upgrade was successful by checking the agent build number in the Acronis management console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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