Local service interruption via named-pipe error exit
Published Dec 3, 2025 · Updated Dec 12, 2025
Denial of service in OpenVPN 2.5.0 through 2.6.16 and 2.7_alpha1 through 2.7_rc2 on Windows allows local users to stop VPN connections. The interactive service's named-pipe accept loop exits on a client connect-and-drop error instead of resetting the pipe, while silent clients can block workers and accumulate handles. Any authenticated local user can interrupt every OpenVPN connection until the service is restarted or the system reboots.
Summary
What happened
Denial of service in OpenVPN 2.5.0 through 2.6.16 and 2.7_alpha1 through 2.7_rc2 on Windows allows local users to stop VPN connections. The interactive service's named-pipe accept loop exits on a client connect-and-drop error instead of resetting the pipe, while silent clients can block workers and accumulate handles. Any authenticated local user can interrupt every OpenVPN connection until the service is restarted or the system reboots.
The record
- CVE
- CVE-2025-13751
- Published
- Dec 3, 2025
- Updated
- Dec 12, 2025
- Vendor
- OpenVPN Inc.
- Product
- OpenVPN
- Classifications
- CWE-775, CWE-770, CWE-841, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Dec 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.5.0 <=2.6.16
- Affected versionversion=2.7_alpha1 <=2.7_rc2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo