Quick answers
- Is CVE-2026-63649 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63649 being exploited in the wild.
- How severe is CVE-2026-63649?
- Informational severity, published 14 August 2026.
- Which products and versions are affected?
- Openvpn 2.4.0 through 2.6.21 and 2.7_alpha1 through 2.7.5.
- Is there a fix for CVE-2026-63649?
- 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-63649 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-63649?
- 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 exists in the Windows interactive service component of OpenVPN, which validates configuration file paths against a whitelist. The flaw allows local authenticated users to craft options that bypass these whitelist checks, enabling them to load arbitrary configuration files outside the trusted configuration directory. An attacker must have local authentication to the system and the ability to supply options to the service. The attack vector is local, requiring existing user-level access. Patches are expected in future OpenVPN releases beyond the affected versions.
Affected products
- OpenVPN OpenVPN 2.4.0 through 2.6.21 and 2.7_alpha1 through 2.7.5
Timeline
- 2026-08-14: disclosed