Quick answers
- Is CVE-2026-105390 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105390 being exploited in the wild.
- How severe is CVE-2026-105390?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Openvpn Ovpn-Dco-Win 0.6.5 through 1.3.3; 2.4.0 through 2.8.7.
- Is there a fix for CVE-2026-105390?
- Yes: fixed in ovpn-dco-win 1.3.4, 2.8.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105390 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-105390?
- Check whether you run Openvpn Ovpn-Dco-Win 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.
How to fix
- Fixed in: ovpn-dco-win 1.3.4, 2.8.13
Technical details
An improper synchronization vulnerability in the ovpn-dco-win kernel driver fails to properly release a device lock across socket send operations, allowing a local attacker to craft a device write that deadlocks the host. The vulnerability is triggered via direct writes to the ovpn-dco device and requires only local access with no elevated privileges. The issue is fixed in ovpn-dco-win 1.3.4 and 2.8.13.
Affected products
- OpenVPN ovpn-dco-win 0.6.5 through 1.3.3; 2.4.0 through 2.8.7
Timeline
- 2026-10-13: disclosed