# CVE-2025-50054: Memory corruption in ovpn-dco-win

> A local attacker can crash the system by sending an oversized control message to the OpenVPN Windows kernel driver.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-c5v3-f4mm-7xmw

## What is CVE-2025-50054?

CVE-2025-50054 is a medium-severity memory corruption vulnerability in OpenVPN ovpn-dco-win, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in OpenVPN ovpn-dco-win version 1.3.0 and earlier and version 2.5.8 and earlier allows a local user process to send a too large control message buffer to the kernel driver resulting in a system crash

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-50054?

It affects 1 product.


Products: Openvpn Ovpn-Dco-Win.

## How do I fix CVE-2025-50054?

No fix has been published for CVE-2025-50054 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50054 being exploited?

There is no known exploitation of CVE-2025-50054 in the wild and no public exploit code.

## Other vulnerabilities in OpenVPN ovpn-dco-win

- [CVE-2026-11604](https://insights.sbomify.com/CVE-2026-11604/): Memory corruption in ovpn-dco-win (medium 5.6)
- [CVE-2024-5198](https://insights.sbomify.com/CVE-2024-5198/): Null dereference in OpenVPN-GUI (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50054 and fix it if it is affected.

What it is: CVE-2025-50054 is a medium-severity memory corruption vulnerability in OpenVPN ovpn-dco-win, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50054 in the wild and no public exploit code.

Affected product: OpenVPN ovpn-dco-win. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-50054/ (Markdown: https://insights.sbomify.com/CVE-2025-50054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50054
- OSV: https://osv.dev/vulnerability/CVE-2025-50054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-50054/
Summaries are generated and may contain mistakes; the official description above is the record.