Quick answers
- Is CVE-2026-84471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84471 being exploited in the wild.
- How severe is CVE-2026-84471?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Openvpn 2.6.0 through 2.6.22 and 2.7_alpha1 through 2.7.6.
- Is there a fix for CVE-2026-84471?
- Yes: fixed in OpenVPN 2.6.23, 2.7.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84471 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-84471?
- 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.
How to fix
- Fixed in: OpenVPN 2.6.23, 2.7.7
Technical details
A use-after-free vulnerability exists in the check_session_buf_not_used() function during TLS session promotion or expiry handling. The flaw requires authentication and the ability to send crafted packets during a specific session state transition. An authenticated remote peer can trigger the vulnerability to cause a denial of service or memory disclosure.
Affected products
- OpenVPN OpenVPN 2.6.0 through 2.6.22 and 2.7_alpha1 through 2.7.6
Timeline
- 2026-10-14: disclosed
- 2026-10-14: patched