Quick answers
- Is CVE-2026-84790 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84790 being exploited in the wild.
- How severe is CVE-2026-84790?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Openvpn 2.3.0 through 2.7.7.
- Is there a fix for CVE-2026-84790?
- Yes: fixed in 2.7.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84790 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-84790?
- 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: 2.7.8
Technical details
The vulnerability is an authentication bypass triggered by improper parsing of certificate subject fields containing embedded NUL bytes. An authenticated remote attacker can exploit this during the certificate validation process to impersonate other identities. The flaw affects OpenVPN 2.3.0 through 2.7.7 and is fixed in version 2.7.8.
Affected products
- OpenVPN OpenVPN 2.3.0 through 2.7.7
Timeline
- 2026-10-13: disclosed
- 2026-10-13: patched: Fixed in version 2.7.8