How severe is CVE-2026-35058?

CVE-2026-35058 has a CVSS 4.0 base score of 6.9, rated medium severity.

Is CVE-2026-35058 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-35058?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-35058 have an EU (EUVD) identifier?

Yes. CVE-2026-35058 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35197.

When was CVE-2026-35058 published?

CVE-2026-35058 was published on 2026-06-08 and last updated on 2026-06-17.

CVE-2026-35058

CVE-2026-35058 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-617.

Key facts

Severity: Medium (CVSS 4.0 base score 6.9)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-35197
Weakness: CWE-617
Published: 2026-06-08
Last modified: 2026-06-17

Description

Improper validation of packet length during tls-crypt-v2 key extraction in OpenVPN 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1 allows authenticated attackers to trigger a fatal assertion and cause a denial of service via a specially crafted packet.

Frequently asked questions

What is CVE-2026-35058?: Improper validation of packet length during tls-crypt-v2 key extraction in OpenVPN 2.6.0 through 2.6.19 and 2.7_alpha1 through 2.7.1 allows authenticated attackers to trigger a fatal assertion and cause a denial of service via a specially crafted packet.
How severe is CVE-2026-35058?: CVE-2026-35058 has a CVSS 4.0 base score of 6.9, rated medium severity.
Is CVE-2026-35058 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-35058?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-35058 have an EU (EUVD) identifier?: Yes. CVE-2026-35058 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35197.
When was CVE-2026-35058 published?: CVE-2026-35058 was published on 2026-06-08 and last updated on 2026-06-17.

References

Other CWE-617 (Reachable Assertion) vulnerabilities

CVE-2020-3615 — Critical (CVSS 9.8): Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue…
CVE-2019-9795 — Critical (CVSS 9.8): A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by…
CVE-2026-31739 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The…
CVE-2020-12417 — High (CVSS 8.8): Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in…
CVE-2020-6623 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index.
CVE-2020-6619 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.

Browse all CWE-617 (Reachable Assertion) vulnerabilities →