dbcve.org
OpenvpnApplication

CVE-2025-13751

MEDIUM · 5.5 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 2.6.17 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Interactive service agent in OpenVPN version 2.5.0 through 2.6.16 and 2.7_alpha1 through 2.7_rc2 on Windows allows a local authenticated user to connect to the service and trigger an error causing a local denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OpenVPN interactive service agent on Windows versions 2.5.0 through 2.6.16 and 2.7_alpha1 through 2.7_rc2 contains a denial of service vulnerability. A locally authenticated Windows user can connect to the interactive service and trigger an error condition that causes the service to become unavailable, disrupting VPN connectivity for the system.

MitigationApply vendor patches for OpenVPN version 2.6.17 or later (or the corresponding 2.7.x stable release). If immediate patching is not feasible, restrict local user access to the system and monitor the OpenVPN service for unexpected failures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenvpnApplication
Affected:>= 2.5.0, < 2.6.17= 2.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenVPN installation on Windows
    Check for OpenVPN installation directory (typically C:\Program Files\OpenVPN or C:\Program Files (x86)\OpenVPN) or look for the OpenVPN service in Windows Services (services.msc)
    Affected if OpenVPN is installed on the system
  2. Determine installed OpenVPN version
    Run 'openvpn --version' from the OpenVPN bin directory, or check the Windows Registry key HKLM\SOFTWARE\OpenVPN, or right-click openvpn.exe and view Properties > Details > File Version
    Affected if The installed version falls within 2.5.0 to 2.6.16, or between 2.7_alpha1 and 2.7_rc2 (including 2.7.0, 2.7_beta1, etc.)
  3. Verify the OpenVPN interactive service exists
    Open Services (services.msc) and look for 'OpenVPN Service' or 'OpenVPN Interactive Service', or run 'sc query openvpnservice' from command prompt
    Affected if The OpenVPN interactive service is present on the system (this is the vulnerable component)
  4. Confirm service is running
    In Services, check the Status column for the OpenVPN service, or run 'sc query state= all' and filter for OpenVPN-related services
    Affected if The OpenVPN service is currently running (an attacker could target it to cause DoS)

A system is affected if OpenVPN for Windows is installed with a version between 2.5.0 and 2.6.16 (inclusive) or any 2.7.x release up to 2.7_rc2, and the OpenVPN interactive service is present and running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.17 or later
Fixed in 2.6.17
Interim mitigation

Apply vendor patches for OpenVPN version 2.6.17 or later (or the corresponding 2.7.x stable release). If immediate patching is not feasible, restrict local user access to the system and monitor the OpenVPN service for unexpected failures.

Recommended fix High confidence

OpenVPN 2.6.17 or later, or fixed 2.7.x release

  1. Download OpenVPN version 2.6.17 or later from the official OpenVPN community website (community.openvpn.net) or your distribution's package repository
  2. Backup your existing OpenVPN configuration files (typically in /etc/openvpn/ or C:\Program Files\OpenVPN\config\)
  3. Install or upgrade to the downloaded OpenVPN version using your system's package manager or installer
  4. Restart the OpenVPN interactive service on Windows: open Services console, find 'OpenVPN Service' or 'OpenVPN Interactive Service', and restart it
  5. Verify the service is running without errors and test VPN connectivity
Caveat Minor: Verify any custom scripts or configurations that interact with the interactive service work correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openvpn Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13751 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data