# OpenVPN fixes two flaws in its Windows interactive service

Canonical: https://www.oktsec.com/radar/openvpn-windows-interactive-service-november-2026
Publisher: Oktsec
Language: en
Published: 2026-11-19T21:08:12Z
Updated: 2026-11-19T21:08:12Z
Record reviewed: 2026-11-19T21:08:12Z
Latest evidence check: 2026-11-19T21:08:12Z
Disclosed: 2026-11-05

A user signed in to an affected Windows endpoint could influence the options or environment used by the OpenVPN interactive service. The service performs privileged operations for the client.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Review this week
- Rationale: Both findings require local authenticated access. The Windows service runs with privileges beyond those of the requesting user.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: OpenVPN
- Products: OpenVPN 2 for Windows
- CVEs: CVE-2026-115342, CVE-2026-121720

## Technical overview

CVE-2026-115342 concerns validation of client options. CVE-2026-121720 concerns the environment inherited by the OpenVPN process. The November 5 release corrects both issues. The exposure is on the Windows endpoint, so updating a VPN gateway alone does not address it.

## Recommended response

Identify Windows endpoints running OpenVPN 2 with the interactive service and update the client to 2.7.9 or a later corrected release.

Relevant to: Administrators of Windows endpoints using OpenVPN 2.

## CVE attribution

- CVE-2026-115342: OpenVPN — OpenVPN 2 for Windows; CVSS 4.0: 8.5. [Source](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/115xxx/CVE-2026-115342.json)
- CVE-2026-121720: OpenVPN — OpenVPN 2 for Windows; CVSS 4.0: 8.5. [Source](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/121xxx/CVE-2026-121720.json)

## Affected systems and fixes

### OpenVPN 2 for Windows

Affected: Windows versions 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 with the interactive service.

Fixed release / action: 2.7.9

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.18
Checked: 2026-11-18T21:06:31.057Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-19T21:12:22.272Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-121720](https://api.first.org/data/v1/epss?cve=CVE-2026-121720): 0.16% probability of observed exploitation in the next 30 days; percentile 4.77%; score date 2026-11-19.
No score returned for: CVE-2026-115342

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-19T21:12:22.272Z.

### Official regional advisories

- [Vulnerabilidades en OpenVPN](https://www.cert.gov.py/vulnerabilidades-en-openvpn/) — CERT-PY, Paraguay; publication 2026-11-19T12:04:09.000Z; observed 2026-11-19T21:12:22.272Z; matched by exact CVE identifier.

Publisher country does not establish victim location. Original notices may repeat the same underlying advisory.

## Response checklist

1. **Find the Windows service** — Distinguish OpenVPN 2 installations from other VPN clients. Include managed laptops and shared Windows hosts.
2. **Deploy the corrected Windows client** — Check the package used by endpoint management, including clients bundled by another vendor.
3. **Confirm the endpoint version** — Verify the installed client version and test a routine connection after rollout.

## Relevance to AI environments

Include Windows automation hosts that use the interactive service to establish VPN connections.

## Sources

- [OpenVPN 2.7.9 release notes](https://github.com/OpenVPN/openvpn/releases/tag/v2.7.9) — OpenVPN; Vendor notice; checked 2026-11-19T21:08:12Z
- [CVE-2026-115342 · vendor CVE record](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/115xxx/CVE-2026-115342.json) — OpenVPN; Vendor notice; checked 2026-11-19T21:08:12Z
- [CVE-2026-121720 · vendor CVE record](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/121xxx/CVE-2026-121720.json) — OpenVPN; Vendor notice; checked 2026-11-19T21:08:12Z

## Editorial record

- 2026-11-19T21:08:12Z: Published the affected Windows client and service, version ranges and corrected release.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/openvpn-windows-interactive-service-november-2026) · [Build a response plan](https://www.oktsec.com/radar/openvpn-windows-interactive-service-november-2026#review-workspace)

- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=openvpn-windows-interactive-service-november-2026&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

