CVE-2026-35058 is a denial-of-service flaw in the OpenVPN server: a crafted control-channel packet that carries a valid tls-crypt-v2 client key trips a fatal assertion and stops the server. NVD scores it 6.5. OpenVPN 2.6.20 and 2.7.2 fix it, servers without tls-crypt-v2 are not affected, and Stormshield lists its SNS firewalls as affected.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
0.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-35058 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| OpenVPN | cpe:2.3:a:openvpn:openvpn:*:*:*:*:*:*:*:* | NVD: 2.6.0 to before 2.6.20 and 2.7 to before 2.7.2; fixed in 2.6.20 and 2.7.2 (OpenVPN announcement) |
| Stormshield Network Security (SNS) firewall appliances | — | SNS 5.1.0 to 5.1.1, 5.0.0 to 5.0.7 and 4.8.0 to 4.8.17; fixed in SNS 5.1.2, 5.0.8 and 4.8.18 (Stormshield STORM-2026-015) |
What does this mean for affected devices?
CVE-2026-35058 is a packet-length validation bug in the OpenVPN server's tls-crypt-v2 handling. The OpenVPN announcement explains that the buffer passed to the function that extracts the wrapped client key still contained the opcode of the received control-channel packet, and that a "too-strict ASSERT" in tls_crypt_unwrap then aborted the process instead of rejecting a short packet. Because an ASSERT ends the whole daemon, one packet takes down every tunnel the server carries, not just the attacker's session.
Exploitation needs a tls-crypt-v2 key. XlabAI of Tencent Xuanwu Lab found a trigger that works with a client key that has a specific byte value, about one key in 256, and OpenVPN says an attacker who obtains such a key or observes a handshake that uses one can crash the server. Cisco Talos independently reported a trigger that works with any tls-crypt-v2 key, but it needs the private part of a client key or the ability to inject packets into a live client session. The announcement states that "setups that do not use tls-crypt-v2 are not affected".
NVD lists the CVE as analyzed and scores it 6.5 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H; OpenVPN as the CNA gives a CVSS 4.0 score of 6.9 and names CWE-617, reachable assertion (NVD). Affected are OpenVPN 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1. The OpenVPN release history shows 2.6.20 and 2.7.2, both released on 22 April 2026, fixing it together with CVE-2026-40215, a TLS handshake race. The Debian security tracker links the upstream fix commit and lists fixed bookworm and trixie packages from DSA-6289-1.
The device angle comes from Stormshield. Its advisory STORM-2026-015, first released on 13 August 2026, covers CVE-2026-35058 and CVE-2026-40215 in Stormshield Network Security (SNS) firewall appliances. Affected are SNS 5.1.0 to 5.1.1, 5.0.0 to 5.0.7 and 4.8.0 to 4.8.17. Stormshield gives no workaround and names SNS 5.1.2, 5.0.8 and 4.8.18 as the fixed releases.
For firmware built from the OpenWrt packages feed, the shipped version decides exposure. Checked on 2026-11-17, the feed's openvpn Makefile builds 2.7.8 on its main branch and on the openwrt-25.12 branch, and the openwrt-24.10 branch builds 2.6.23, all later than the fix. The openwrt-23.05 branch builds 2.5.8, which is outside NVD's affected range.
The CVE is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00541, the 46th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
On a gateway image, read the OpenVPN version from the package database or the OpenVPN 2.x.y string in the binary, then check the server configuration for a tls-crypt-v2 line. Our OpenVPN and strongSwan firmware guide shows how to find the VPN stack in an image and ranks this CVE against the other OpenVPN and strongSwan flaws. The same OpenVPN server code also carried the older CVE-2022-0547 deferred-auth plug-in bypass, and our patch management guide covers rolling a fixed release out to a device fleet.
Evidence
- Opcode not skipped before reading the wrapped client key, and a too-strict ASSERT in tls_crypt_unwrap; XlabAI trigger needs a client key with a specific byte value (about 1/256); Talos trigger needs the private part of a client key or packet injection into a live session; setups without tls-crypt-v2 are not affected; 2.6.0 to 2.6.19 and 2.7_alpha1 to 2.7.1 affected, fixed in 2.6.20 and 2.7.2. — OpenVPN announcement
- NVD status Analyzed; NVD Primary CVSS v3.1 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H); OpenVPN CNA CVSS 4.0 6.9 and CWE-617; CPE ranges 2.6.0 to before 2.6.20 and 2.7 to before 2.7.2. — NVD
- OpenVPN 2.6.20 and 2.7.2 released 22 April 2026 with security fixes for CVE-2026-35058 and CVE-2026-40215. — OpenVPN release history
- Debian lists the upstream fix commit and fixed bookworm and trixie packages from DSA-6289-1. — Debian security tracker
- STORM-2026-015 (v1 13 August 2026): SNS 5.1.0 to 5.1.1, 5.0.0 to 5.0.7 and 4.8.0 to 4.8.17 affected by CVE-2026-35058 and CVE-2026-40215; no workaround; fixed in SNS 5.1.2, 5.0.8 and 4.8.18. — Stormshield STORM-2026-015
- OpenWrt packages feed, checked 2026-11-17: openvpn 2.7.8 on the main branch and openwrt-25.12, 2.6.23 on openwrt-24.10, 2.5.8 on openwrt-23.05. — OpenWrt packages feed
- Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00541 (46th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories
Sources
- NVD
- OpenVPN announcement CVE-2026-35058: server ASSERT with a valid tls-crypt-v2 key
- OpenVPN community wiki: Release history (2.6.20 and 2.7.2)
- Stormshield STORM-2026-015: multiple vulnerabilities in OpenVPN (SNS)
- Debian security tracker: CVE-2026-35058
- OpenWrt packages feed: openvpn Makefile
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which OpenVPN versions are affected by CVE-2026-35058?
OpenVPN 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1. Versions 2.6.20 and 2.7.2, released on 22 April 2026, fix it (per the OpenVPN announcement and release history).
Is every OpenVPN server exposed to CVE-2026-35058?
No. Only servers that use tls-crypt-v2 are affected, and the attacker needs a suitable tls-crypt-v2 client key, an observed handshake that uses one, or the ability to inject packets into a live client session (per the OpenVPN announcement).
Which firewalls are affected by CVE-2026-35058?
Stormshield lists its Stormshield Network Security (SNS) appliances: SNS 5.1.0 to 5.1.1, 5.0.0 to 5.0.7 and 4.8.0 to 4.8.17, fixed in SNS 5.1.2, 5.0.8 and 4.8.18, with no workaround (per Stormshield STORM-2026-015).
Is CVE-2026-35058 exploited?
It is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00541, the 46th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?