Memory Leak in OpenVPN TLS-Crypt-V2 Client Key

Publication date: 2026-07-06

Last updated on: 2026-07-09

Assigner: OpenVPN Inc.

Description

A memory leak in OpenVPN version 2.5.0 through 2.5.11, 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote attackers with a valid tls-crypt-v2 client key to potentially cause a denial of service

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-06

Last Modified

2026-07-09

Generated

2026-07-28

AI Q&A

2026-07-06

EPSS Evaluated

2026-07-26

NVD

CVE-2026-13698

EUVD

EUVD-2026-41877

Affected Vendors & Products

Vendor	Product	Version / Range
openvpn	openvpn	From 2.6.0 (inc) to 2.6.21 (exc)
openvpn	openvpn	From 2.7 (inc) to 2.7.5 (exc)
openvpn	openvpn	From 2.5.0 (inc) to 2.5.11 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-401	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
CWE-770	The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

Executive Summary

This vulnerability is a memory leak found in OpenVPN versions 2.5.0 through 2.5.11, 2.6.0 through 2.6.20, and 2.7_alpha1 through 2.7.4. It allows remote attackers who possess a valid tls-crypt-v2 client key to potentially cause a denial of service.

Impact Analysis

The impact of this vulnerability is that an attacker with a valid tls-crypt-v2 client key can exploit the memory leak to cause a denial of service, potentially disrupting the availability of the OpenVPN service.

Hi! I’m here to help you understand CVE-2026-13698. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70