Improper validation of packet length during tls-crypt-v2 key extraction in OpenVPN 2.6.0 through 2.6.19 and 2.7_alpha1
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 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 10 Nov 2026.
What to do
AI-suggested
Until a fix is released, restrict access to trusted users and monitor for abnormal OpenVPN service crashes.
Description
OpenVPN versions 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1 contain a vulnerability in the tls-crypt-v2 key extraction process due to improper validation of packet length. This flaw allows authenticated attackers to send specially crafted packets that trigger a fatal assertion, resulting in a denial of service condition.
References
- nvd.nist.gov/vuln/detail/CVE-2026-35058 (opens in a new tab)
- community.openvpn.net/ReleaseHistory (opens in a new tab)
- community.openvpn.net/ReleaseHistory (opens in a new tab)
- community.openvpn.net/Security%20Announcements/CVE-2026-35058 (opens in a new tab)
- talosintelligence.com/vulnerability_reports/TALOS-2026-2381 (opens in a new tab)