CVE-2023-46850: OpenVPN 2 (Community) · Use After Free
Affects OpenVPN 2 (Community)Source CVE Database V5
Not known to be exploited.
Data as of 25 Oct 2026, 19:02 UTC
Rated High by the CNA (OpenVPN) · No CVSS score from NVD or the CNA
- EPSS
- 1.9% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Debiandebian/openvpnpkg:deb/debian/openvpnOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor OpenVPN vendor communications closely and apply security patches immediately once they become available for versions 2.6.0 through 2.6.6. 2. Until patches are released, restrict OpenVPN traffic to trusted IP addresses and networks using firewall rules or network segmentation to reduce exposure to untrusted sources. 3. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous OpenVPN traffic patterns indicative of exploitation attempts. 4. Conduct regular audits of VPN server and client configurations to ensure minimal exposure and adherence to security best practices, including disabling unnecessary features or protocols. 5. Implement robust logging and monitoring of VPN endpoints to detect unusual activity or crashes that may indicate exploitation attempts. 6. Educate network administrators and security teams about this vulnerability to ensure rapid response and incident handling. 7. Consider deploying network-level mitigations such as rate limiting or deep packet inspection for OpenVPN traffic to identify and block malformed packets. 8. Evaluate alternative VPN solutions or versions not affected by this vulnerability if immediate patching is not feasible.
Description
CVE-2023-46850 is a use-after-free vulnerability in OpenVPN Community Edition versions 2.6.0 through 2.6.6. This flaw arises when network buffers are sent to a remote peer, potentially causing undefined behavior, memory leaks, or remote code execution. Exploitation does not require authentication but involves network interaction with a vulnerable OpenVPN server or client. Although no known exploits are currently reported in the wild, successful exploitation could compromise confidentiality, integrity, and availability of VPN communications. European organizations relying on OpenVPN for secure remote access and site-to-site VPNs are at risk, especially critical infrastructure and enterprises with high VPN usage. Mitigation involves promptly updating to patched versions once available, employing network-level filtering to restrict OpenVPN traffic, and monitoring for anomalous VPN behavior.
References
- community.openvpn.net/openvpn/wiki/CVE-2023-46850 (opens in a new tab)
- openvpn.net/security-advisory/access-server-security-update-cve-2023-46849-cve-2023-46850/ (opens in a new tab)
- debian.org/security/2023/dsa-5555 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L3FS46ANNTAVLIQY56ZKGM5CBTRVBUNE/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O54I7D753V6PU6XBU26FEROD2DSHEJQ4/ (opens in a new tab)