CVE-2026-13698

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory published 2026-07-06. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
7.5
EG Score
7.5(high)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
42.6%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Vendor Advisories for CVE-2026-13698(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenvpn (2.5.11-0ubuntu0.22.04.4) @ jammy2026-07-16ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 19:34 UTCVendor advisory
  10. 2026-07-16 19:34 UTCGHSA enrichment
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 07:55 UTCVendor advisory
  13. 2026-07-16 07:55 UTCGHSA enrichment
  14. 2026-07-15 20:18 UTCVendor advisory
  15. 2026-07-15 20:18 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 08:41 UTCVendor advisory
  18. 2026-07-15 08:41 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 21:02 UTCVendor advisory
  21. 2026-07-14 21:02 UTCGHSA enrichment
  22. 2026-07-14 09:24 UTCGHSA enrichment
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 21:45 UTCGHSA enrichment
  25. 2026-07-13 10:07 UTCGHSA enrichment
Show 20 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 22:20 UTCGHSA enrichment
  3. 2026-07-12 10:42 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 23:04 UTCGHSA enrichment
  6. 2026-07-11 11:27 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 23:50 UTCGHSA enrichment
  9. 2026-07-10 12:13 UTCEG score recompute 1.50
  10. 2026-07-10 12:13 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 13:52 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  13. 2026-07-09 12:45 UTCGHSA enrichment
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 13:17 UTCGHSA enrichment
  17. 2026-07-07 13:48 UTCGHSA enrichment
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 14:22 UTCEG score recompute
  20. 2026-07-06 14:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13698?
CVE-2026-13698 is a high vulnerability published on July 6, 2026. 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
When was CVE-2026-13698 disclosed?
CVE-2026-13698 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13698 actively exploited?
CVE-2026-13698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13698?
CVE-2026-13698 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-13698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13698, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13698

Explore →

Is Your Infrastructure Affected by CVE-2026-13698?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.