Skip to main content
Menu
CVEs

CVE

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.

CVE-2026-121720EUVD-2026-129307Published Updated Summary written by a model

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.7.9
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Runs on Windows with the OpenVPN Windows Interactive Service Affected versions are OpenVPN 2.4.0 through 2.7.8

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.

Original 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.

Who should check

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

“OpenVPN versions 2.4.0 through 2.7.8 are affected.”

community.openvpn.net

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Runs on Windows with the OpenVPN Windows Interactive Service Affected versions are OpenVPN 2.4.0 through 2.7.8
  • Upgrade to a fixed version: 2.7.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • OpenVPN OpenVPN

    From 2.4.0 · through 2.6.23; From 2.7_alpha1 · through 2.7.8

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorycommunity.openvpn.net · Security Announcements/CVE-2026-121720
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-121720
RecordNVD · CVE-2026-121720
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · refiaa/CVE-2026-121720 · Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-121720

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: cve.now feed data

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: community.openvpn.net

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: cve.now feed data

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: community.openvpn.net

How do I fix CVE-2026-121720?

Upgrade to OpenVPN 2.7.9, the version the advisory names as the fix.Source: community.openvpn.net

More CVEs