Skip to main content
Menu
CVEs

OpenVPN arbitrary config injection in Windows interactive service

Only affects OpenVPN on Windows from 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8, via the interactive service. Fixed in 2.7.9.

CVE-2026-115342Published November 19, 2026, updated

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

Summary

Argument injection in OpenVPN on Windows lets a local user with low-privilege login bypass the interactive service's option validation and add arbitrary configuration options through a crafted command line. The flaw can be reached only from the local machine, not over the network.

Written by a model

Original description

Argument injection in OpenVPN version 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to bypass interactive service option validation and add arbitrary configuration options via a crafted command line.

Who should check

Windows teams running OpenVPN 2.4.0 through 2.7.8 with the Windows interactive service.

“OpenVPN versions 2.4.0 through 2.7.8 are affected.”

community.openvpn.net

What to do

  1. Check whether your setup matches what the bug needs.

    Runs on Windows, where the OpenVPN interactive service validates command-line options. OpenVPN versions 2.4.0 through 2.7.8.
  2. 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-115342 (Argument injection in OpenVPN version 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to…), 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-115342 (entry last updated 2026-11-19):
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, where the OpenVPN interactive service validates command-line options. (source: https://community.openvpn.net/Security%20Announcements/CVE-2026-115342)
- OpenVPN versions 2.4.0 through 2.7.8. (source: https://community.openvpn.net/Security%20Announcements/CVE-2026-115342)
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-115342 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115342 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-115342
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-115342
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-115342"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • 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

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

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorycommunity.openvpn.net · Security Announcements/CVE-2026-115342
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-115342
RecordNVD · CVE-2026-115342

Questions about CVE-2026-115342

Is CVE-2026-115342 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 crafted command line can hide restricted options from the OpenVPN interactive service's validator, while openvpn.exe still executes them. This bypasses the rule that configuration files load only from the locked-down OpenVPN configuration directory.

Source: community.openvpn.net

Which versions are affected by CVE-2026-115342?

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 affects OpenVPN versions 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows, where the interactive service validates command-line options. Compare the installed OpenVPN version against these ranges to check.

Source: community.openvpn.net

How do I fix CVE-2026-115342?

Upgrade to OpenVPN 2.7.9, which the advisory names as the fixed version.

Source: community.openvpn.net

No corrections so far. Something wrong on this page? Report an error.