CVE-2026-121720: OpenVPN · External Initialization of Trusted Variables or Data Stores
Affects OpenVPNSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 18 Nov 2026, 22:04 UTC
Thin evidence
One scorer or none| CNA (OpenVPN) | CVSS 4.0 | 8.5 |
|---|
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- Attack Vector
- Local
- Attack Complexity
- Low
- Attack Requirements
- None
- Privileges Required
- Low
- User Interaction
- None
- Vulnerable system confidentiality
- High
- Vulnerable system integrity
- High
- Vulnerable system availability
- High
- Subsequent system confidentiality
- None
- Subsequent system integrity
- Low
- Subsequent system availability
- Low
Bold values are the worst case: easiest to exploit or largest impact.
- Attack Vector: Local
- The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
- Attack Complexity: Low
- The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
- Attack Requirements: None
- The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
- Privileges Required: Low
- The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
- User Interaction: None
- The vulnerable system can be exploited without interaction from any human user, other than the attacker.
- Vulnerable system confidentiality: High
- There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
- Vulnerable system integrity: High
- There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
- Vulnerable system availability: High
- There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
- Subsequent system confidentiality: None
- There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
- Subsequent system integrity: Low
- Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
- Subsequent system availability: Low
- Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Subsequent System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Subsequent System.
Definitions: FIRST CVSS v4.0 specification.
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
- Disclosed
- The CVE record is public on cve.org. Its publication is t = 0.
- Detectable
- A public nuclei template can find exposed instances, for defenders and attackers alike.
- Weaponized
- A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
- Exploited in the wild
- CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
- Observed by OffSeq Mirage
- OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.
Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenVPNOpenVPN | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict local authenticated user access and monitor for suspicious activity related to environment variable manipulation.
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.
Impact
Successful exploitation allows local authenticated users to execute arbitrary code with elevated privileges via a privileged OpenVPN service on Windows. This could lead to full system compromise or unauthorized actions performed with the service's privileges.
Proofs of concept on GitHub
Public tooling indexed from Metasploit Framework, Exploit-DB, ProjectDiscovery nuclei-templates and PoC-in-GitHub. Its existence raises the odds of exploitation; it does not confirm attacks.
- CWE-454External Initialization of Trusted Variables or Data Stores (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.
Implementation · Input Validation
A product system should be reluctant to trust variables that have been initialized outside of its trust boundary, especially if they are initialized by users. Ensure adequate checking (e.g. input validation) is performed when relying on input from outside a trust boundary.
Architecture and Design
Avoid any external control of variables. If necessary, restrict the variables that can be modified using an allowlist, and use a different namespace or naming convention if possible.
- OWASP Cheat Sheets
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
- CWE-426Untrusted Search Path (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.
Architecture and Design · Implementation · Attack Surface Reduction
Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
Implementation
When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames.
Implementation
Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
- OWASP Cheat Sheets
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
- CWE-250Execution with Unnecessary Privileges (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
Architecture and Design · Separation of Privilege
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
Architecture and Design · Attack Surface Reduction
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
- OWASP Cheat Sheets
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
- Cvss Sources
- [object Object]
- Assigned by (CNA)
- OpenVPN Inc. (opens in a new tab) · Vendor, Open Source · USA
- Reserved
- CVSS version
- 4.0
References
Community reviews
Related threats
- CVE-2024-5594: OpenVPN · Improper Validation of Specified Type of InputCriticalVulnerability
- Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement updateHighVulnerability
- Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement updateHighVulnerability
- Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement updateHighVulnerability
- ASUS Armoury Crate · Untrusted Search PathHighVulnerability