Quick answers
- Is CVE-2026-82312 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82312 being exploited in the wild.
- How severe is CVE-2026-82312?
- Informational severity, published 7 September 2026.
- Which products and versions are affected?
- Openvpn 2.0.0 through 2.6.22, 2.7_alpha1 through 2.7.6 on Windows.
- Is there a fix for CVE-2026-82312?
- 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-82312 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-82312?
- Check whether you run Openvpn 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
This vulnerability affects OpenVPN's handling of Windows named IPC objects, which use NULL DACL (Discretionary Access Control List) for permission management. The weakness allows any local authenticated user on the system to interfere with these IPC channels, leading to denial of service against the VPN service. The attack requires local system access and authentication but does not require network access. An attacker can crash or disable the OpenVPN service, disrupting VPN connectivity for legitimate users. Patches are available in newer versions beyond 2.6.22 and 2.7.6.
Affected products
- OpenVPN OpenVPN 2.0.0 through 2.6.22, 2.7_alpha1 through 2.7.6 on Windows
Timeline
- 2026-09-07: disclosed