dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-41220

HIGH · 7.8 CVSS v3.0 Published 2026-04-29
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 improper input validation. The following products are affected: Acronis DeviceLock DLP (Windows) before build 9.0.93212, Acronis Cyber Protect Cloud Agent (Windows) before build 42183.

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 security products for Windows stemming from improper input validation. The flaw allows a local attacker with low-privilege access to elevate to SYSTEM or administrator privileges by exploiting insufficient validation of user-supplied input. Affected products are DeviceLock DLP versions before build 9.0.93212 and Cyber Protect Cloud Agent versions before build 42183.

MitigationApply vendor-supplied updates to upgrade to build 9.0.93212 or later for DeviceLock DLP, and build 42183 or later for Cyber Protect Cloud Agent. As this is a local privilege escalation, ensure least-privilege principles are followed for accounts on systems running these products.

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. Identify installed Acronis security products
    Review the list of installed software on the Windows system to determine if DeviceLock DLP or Cyber Protect Cloud Agent is present. Check Add/Remove Programs, Programs and Features, or query the Windows Installer database.
    Affected if Either DeviceLock DLP or Cyber Protect Cloud Agent is installed on the system
  2. Check DeviceLock DLP build version
    Locate the DeviceLock DLP installation directory or executable file (typically found in Program Files). Right-click the main executable, select Properties, and view the Details tab to find the File Version or Product Version. Alternatively, check the version information displayed by the DeviceLock management interface.
    Affected if The installed build number is lower than 9.0.93212
  3. Check Cyber Protect Cloud Agent build version
    Locate the Cyber Protect Cloud Agent installation directory or executable file (typically found in Program Files or ProgramData). Right-click the main executable, select Properties, and view the Details tab to find the File Version or Product Version. Alternatively, check the version through the Acronis management console or agent status interface.
    Affected if The installed build number is lower than 42183
  4. Confirm the vulnerable service or component is enabled
    Verify that the Acronis service related to the affected component is running. Check Windows Services for the Acronis service entries and confirm they are in a Running state. The privilege escalation requires the vulnerable code path to be active.
    Affected if The Acronis service associated with the affected product is installed and running

A system is affected if either DeviceLock DLP with a build below 9.0.93212 or Cyber Protect Cloud Agent with a build below 42183 is installed and running on Windows.

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

Apply vendor-supplied updates to upgrade to build 9.0.93212 or later for DeviceLock DLP, and build 42183 or later for Cyber Protect Cloud Agent. As this is a local privilege escalation, ensure least-privilege principles are followed for accounts on systems running these products.

Recommended fix High confidence

Acronis DeviceLock DLP build 9.0.93212 or later; Acronis Cyber Protect Cloud Agent build 42183 or later

  1. 1. Identify the currently installed version of Acronis DeviceLock DLP on Windows systems
  2. 2. Identify the currently installed version of Acronis Cyber Protect Cloud Agent on Windows systems
  3. 3. For Acronis DeviceLock DLP: upgrade to build 9.0.93212 or later by obtaining the updated installer from Acronis support or management console
  4. 4. For Acronis Cyber Protect Cloud Agent: upgrade to build 42183 or later by obtaining the updated installer from Acronis support or management console
  5. 5. Verify the upgrade was successful by checking the build number in the product UI or via PowerShell/command-line
  6. 6. Test that the Acronis services start正常运行 and DLP/protection functionality is operational
  7. 7. Document the update in the change management system
Caveat Standard upgrade risk - test in non-production environment before deploying broadly; ensure backups are current

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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