Quick answers
- Is CVE-2026-82325 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82325 being exploited in the wild.
- How severe is CVE-2026-82325?
- Informational severity, published 7 September 2026.
- Which products and versions are affected?
- Openvpn Ovpn-Dco-Win 2.5.0 through 2.8.6.
- Is there a fix for CVE-2026-82325?
- 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-82325 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-82325?
- 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.
Technical details
A use-after-free vulnerability exists in the OpenVPN ovpn-dco-win driver versions 2.5.0 through 2.8.6 in the handling of control messages. An authenticated local attacker can craft specially formed control messages to trigger access to memory that has already been freed, causing a kernel panic or system crash. The attack requires local authentication and the ability to send crafted control messages to the driver. Use-after-free flaws can potentially be escalated beyond denial of service, though current evidence indicates the primary impact is system crash.
Affected products
- OpenVPN ovpn-dco-win 2.5.0 through 2.8.6
Timeline
- 2026-09-07: disclosed