# CVE-2026-25852: Privilege escalation in Acronis DeviceLock DLP

> Local attackers can escalate privileges via DLL hijacking in Acronis DeviceLock DLP, requiring an upgrade to the latest build.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-hxj2-hjxp-rpjq

## What is CVE-2026-25852?

CVE-2026-25852 is a medium-severity vulnerability in Acronis DeviceLock DLP, published on 29 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Local privilege escalation due to DLL hijacking vulnerability. The following products are affected: Acronis DeviceLock DLP (Windows) before build 9.0.93212.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-25852?


## How do I fix CVE-2026-25852?

No fix has been published for CVE-2026-25852 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25852 being exploited?

There is no known exploitation of CVE-2026-25852 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25852 and fix it if it is affected.

What it is: CVE-2026-25852 is a medium-severity vulnerability in Acronis DeviceLock DLP, published on 29 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25852 in the wild and no public exploit code.

Affected product: Acronis DeviceLock DLP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25852/ (Markdown: https://insights.sbomify.com/CVE-2026-25852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25852
- OSV: https://osv.dev/vulnerability/CVE-2026-25852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25852/
Summaries are generated and may contain mistakes; the official description above is the record.