Quick answers
- Is CVE-2026-44609 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44609 being exploited in the wild.
- How severe is CVE-2026-44609?
- High severity, with a CVSS score of 7.3, published 3 June 2026.
- Which products and versions are affected?
- Acronis DeviceLock DLP before build 9.0.15051.93227.
- Is there a fix for CVE-2026-44609?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44609 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-44609?
- Check whether you run Acronis DeviceLock DLP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A local privilege escalation vulnerability exists in Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227 due to an uncontrolled search path (CWE-427), commonly referred to as EXE hijacking. The application fails to properly validate or restrict the search path used to locate and execute binary files. A local attacker with low-level privileges can exploit this by placing a malicious executable in a directory that the application searches before the legitimate binary's location. Successful exploitation requires some user interaction and allows the attacker to execute arbitrary code with the elevated privileges of the DeviceLock service or application.
Affected products
- Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227
Timeline
- 2026-06-03: disclosed
- 2026-06-03: advisory