Quick answers
- Is CVE-2026-12932 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12932 being exploited in the wild.
- How severe is CVE-2026-12932?
- Informational severity, with a CVSS score of 7.1, published 30 July 2026.
- Which products and versions are affected?
- Openvpn 2.5.0 through 2.6.20, 2.7_alpha1 through 2.7.4.
- Is there a fix for CVE-2026-12932?
- A patch was published on 2026-07-01: OpenVPN versions 2.6.21 and 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-12932 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12932?
- 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
A memory leak vulnerability (CWE-401) exists in OpenVPN's tls-crypt-v2 client key extraction component. The flaw is triggered during the processing of crafted packets, where the application fails to release memory after its effective lifetime. A remote attacker with low privileges can exploit this over the network by flooding the service with these packets, leading to memory exhaustion and a Denial of Service (DoS) condition. The issue affects versions 2.5.0 through 2.6.20 and 2.7_alpha1 through 2.7.4, and has been addressed in versions 2.6.21 and 2.7.5.
Affected products
- OpenVPN OpenVPN 2.5.0 through 2.6.20, 2.7_alpha1 through 2.7.4
Timeline
- 2026-07-01: patched: OpenVPN versions 2.6.21 and 2.7.5 released to address the issue.
- 2026-07-30: advisory: CVE-2026-12932 published.