Quick answers
- Is CVE-2026-13117 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13117 being exploited in the wild.
- How severe is CVE-2026-13117?
- Informational severity, with a CVSS score of 6, published 30 July 2026.
- Which products and versions are affected?
- OpenVPN Inc. OpenVPN 2.6.0 through 2.6.20, 2.7_alpha1 through 2.7.4.
- Is there a fix for CVE-2026-13117?
- A patch was published on 2026-07-01: Fixed in versions 2.6.21 and 2.7.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13117 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-13117?
- 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 use-after-free (UAF) vulnerability exists in OpenVPN versions 2.6.0-2.6.20 and 2.7_alpha1-2.7.4 due to an incomplete guard during TLS session promotion. An authenticated remote peer can exploit this flaw by sending specifically crafted sequences during the session promotion phase. Successful exploitation can lead to a crash of the OpenVPN process (Denial of Service) or the leakage of sensitive memory contents. The vulnerability is tracked as CWE-416 and has been addressed in OpenVPN versions 2.6.21 and 2.7.5.
Affected products
- OpenVPN Inc. OpenVPN 2.6.0 through 2.6.20, 2.7_alpha1 through 2.7.4
Timeline
- 2026-07-01: patched: Fixed in versions 2.6.21 and 2.7.5
- 2026-07-30: disclosed: CVE-2026-13117 published