Quick answers
- Is CVE-2026-81738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81738 being exploited in the wild.
- How severe is CVE-2026-81738?
- Informational severity, published 7 September 2026.
- Which products and versions are affected?
- Openvpn 2.5.0 through 2.7.6.
- Is there a fix for CVE-2026-81738?
- 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-81738 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-81738?
- 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
The vulnerability is an out-of-bounds write condition in the tap-windows6 driver component used by OpenVPN on Windows. The flaw is triggered via crafted DOMAIN-SEARCH entries in OpenVPN configuration, allowing an attacker on the network to send specially crafted packets that exploit insufficient input validation. The attack is network-reachable and does not require prior authentication. Successful exploitation could result in denial of service (driver crash) or potentially arbitrary code execution with system privileges, depending on memory layout and exploitation technique. Versions 2.5.0 through 2.7.6 are affected; patched versions are expected from the OpenVPN project.
Affected products
- OpenVPN OpenVPN 2.5.0 through 2.7.6
Timeline
- 2026-09-07: disclosed