Is CVE-2026-35058 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35058 being exploited in the wild.

How severe is CVE-2026-35058?

Informational severity, with a CVSS score of 6.9, published 8 June 2026.

Which products and versions are affected?

OpenVPN Inc. OpenVPN 2.6.0 through 2.6.19, 2.7_alpha1 through 2.7.1.

Is there a fix for CVE-2026-35058?

A patch was published on 2026-04-22: Fixed in OpenVPN 2.6.20 and 2.7.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35058 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-35058?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35058: OpenVPN denial of service via reachable assertion in tls-crypt-v2

CVE-2026-35058 · Severity: info · CVSS 6.9 · Published 2026-06-08

OpenVPN is a widely used software for creating secure private network connections. A vulnerability in how it handles specific encrypted packets allows an authorized user to crash the VPN server. This results in a denial of service, preventing other users from connecting or maintaining their secure sessions until the service is restarted.

Quick answers

Is CVE-2026-35058 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35058 being exploited in the wild.
How severe is CVE-2026-35058?: Informational severity, with a CVSS score of 6.9, published 8 June 2026.
Which products and versions are affected?: OpenVPN Inc. OpenVPN 2.6.0 through 2.6.19, 2.7_alpha1 through 2.7.1.
Is there a fix for CVE-2026-35058?: A patch was published on 2026-04-22: Fixed in OpenVPN 2.6.20 and 2.7.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35058 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-35058?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A reachable assertion vulnerability (CWE-617) exists in OpenVPN's tls-crypt-v2 key extraction logic. The software fails to properly validate packet lengths before processing, which can be triggered by an authenticated attacker sending a specially crafted packet. This results in a fatal assertion that crashes the OpenVPN process, leading to a denial of service. The vulnerability affects versions 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1, and has been addressed in versions 2.6.20 and 2.7.2.

Affected products

OpenVPN Inc. OpenVPN 2.6.0 through 2.6.19, 2.7_alpha1 through 2.7.1

Timeline

2026-04-22: patched: Fixed in OpenVPN 2.6.20 and 2.7.2
2026-06-08: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.