Quick answers
- Is CVE-2026-13379 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13379 being exploited in the wild.
- How severe is CVE-2026-13379?
- Informational severity, with a CVSS score of 5.1, published 30 July 2026.
- Which products and versions are affected?
- OpenVPN Inc. OpenVPN 2.7_alpha1 through 2.7.4.
- Is there a fix for CVE-2026-13379?
- A patch was published on 2026-07-01: OpenVPN 2.7.5 released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13379 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-13379?
- Check whether anything you run is named in the advisory. 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 vulnerability exists in the Windows interactive service of OpenVPN (versions 2.7_alpha1 through 2.7.4) involving improper neutralization of value delimiters and an out-of-bounds read (CWE-142, CWE-125). An attacker can exploit this by providing a specially crafted search domain that is processed during the VPN disconnection phase. Successful exploitation can lead to a persistent corrupted DNS state on the host or a denial-of-service (DoS) via a service crash. The attack requires low privileges and some user interaction, but can be initiated over the network. The issue is addressed in OpenVPN version 2.7.5.
Affected products
- OpenVPN Inc. OpenVPN 2.7_alpha1 through 2.7.4
Timeline
- 2026-07-01: patched: OpenVPN 2.7.5 released to address the issue
- 2026-07-30: advisory: CVE-2026-13379 published by OpenVPN Inc. and NVD