Quick answers
- Is CVE-2026-78043 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78043 being exploited in the wild.
- How severe is CVE-2026-78043?
- Informational severity, published 7 September 2026.
- Which products and versions are affected?
- Openvpn 2.7_alpha1 through 2.7.6.
- Is there a fix for CVE-2026-78043?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78043 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-78043?
- 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
The vulnerability is a path traversal / trust boundary bypass in the Windows Interactive Service component of OpenVPN 2.7_alpha1 through 2.7.6. The service enforces a trusted configuration directory constraint to prevent unprivileged users from loading arbitrary configuration files; however, specially crafted paths can be used to circumvent this restriction. The attack requires local authentication (an existing user account on the system) and does not require network access. A successful exploit allows an authenticated local user to load and execute arbitrary configuration files, potentially compromising the VPN client's security posture.
Affected products
- OpenVPN OpenVPN 2.7_alpha1 through 2.7.6
Timeline
- 2026-09-07: disclosed