A memory leak in the tls-crypt-v2 client key extraction in OpenVPN 2.5.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote attackers to cause a denial of service (memory exhaustion) via a flood of crafted packets
CVE-2026-12932
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. NVD baseline CVSS 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 5, 2026
References (3)
Vendor Advisories for CVE-2026-12932(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | openvpn (2.5.11-0ubuntu0.22.04.4) @ jammy | 2026-08-20 | ubuntu |
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.
Affected Packages
(5 across 5 ecosystems)
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvpn | — | 2.7.5-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvpn | 2.5.1-3 ... 2.7.5-1~bpo13+1 (63 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvpn | 2.6.11-1 ... 2.6.9-1 (15 versions) | 2.6.14-0+deb12u2 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvpn | 2.6.14-1, 2.6.14-1+deb13u1, 2.6.14-1+deb13u2 | 2.6.14-1+deb13u3 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvpn | 2.6.14-1 ... 2.7.5-1~bpo13+1 (24 versions) | 2.7.5-1 | — |
Weakness Classification(1)
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 40× in last 7d / 131× 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.
Showing the most recent 100 of 131 total refreshes for this CVE.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:03 UTCVendor advisory
- 2026-08-20 21:03 UTCGHSA enrichment
- 2026-08-20 09:00 UTCVendor advisory
- 2026-08-20 09:00 UTCGHSA enrichment
- 2026-08-19 20:58 UTCEG score recompute
- 2026-08-19 20:58 UTCVendor advisory
- 2026-08-19 20:58 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 08:55 UTCVendor advisory
- 2026-08-19 08:55 UTCGHSA enrichment
- 2026-08-18 20:48 UTCEG score recompute
- 2026-08-18 20:48 UTCVendor advisory
- 2026-08-18 20:48 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 08:46 UTCVendor advisory
- 2026-08-18 08:46 UTCGHSA enrichment
- 2026-08-17 20:45 UTCEG score recompute
- 2026-08-17 20:44 UTCGHSA enrichment
- 2026-08-17 08:40 UTCVendor advisory
- 2026-08-17 08:40 UTCGHSA enrichment
- 2026-08-16 20:38 UTCEG score recompute
- 2026-08-16 20:38 UTCVendor advisory
- 2026-08-16 20:38 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-16 08:36 UTCEG score recompute
- 2026-08-16 08:36 UTCVendor advisory
- 2026-08-16 08:36 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:34 UTCVendor advisory
- 2026-08-15 20:34 UTCGHSA enrichment
- 2026-08-15 08:32 UTCEG score recompute
- 2026-08-15 08:32 UTCVendor advisory
- 2026-08-15 08:32 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 20:29 UTCVendor advisory
- 2026-08-14 20:29 UTCGHSA enrichment
- 2026-08-14 08:27 UTCEG score recompute
- 2026-08-14 08:27 UTCVendor advisory
- 2026-08-14 08:27 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 20:25 UTCVendor advisory
- 2026-08-13 20:25 UTCGHSA enrichment
- 2026-08-13 08:18 UTCVendor advisory
- 2026-08-13 08:18 UTCGHSA enrichment
- 2026-08-12 20:17 UTCEG score recompute
- 2026-08-12 20:17 UTCVendor advisory
- 2026-08-12 20:17 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 08:15 UTCVendor advisory
- 2026-08-12 08:15 UTCGHSA enrichment
- 2026-08-11 20:13 UTCEG score recompute
- 2026-08-11 20:13 UTCVendor advisory
- 2026-08-11 20:13 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 08:12 UTCEG score recompute
- 2026-08-11 08:12 UTCVendor advisory
- 2026-08-11 08:12 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 20:10 UTCVendor advisory
- 2026-08-10 20:10 UTCGHSA enrichment
- 2026-08-10 08:08 UTCVendor advisory
- 2026-08-10 08:08 UTCGHSA enrichment
- 2026-08-09 20:06 UTCEG score recompute
- 2026-08-09 20:06 UTCVendor advisory
- 2026-08-09 20:06 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:05 UTCVendor advisory
- 2026-08-09 08:05 UTCGHSA enrichment
- 2026-08-08 20:03 UTCEG score recompute
- 2026-08-08 20:03 UTCVendor advisory
- 2026-08-08 20:03 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 08:01 UTCVendor advisory
- 2026-08-08 08:01 UTCGHSA enrichment
- 2026-08-07 19:59 UTCEG score recompute
- 2026-08-07 19:59 UTCVendor advisory
- 2026-08-07 19:59 UTCGHSA enrichment
- 2026-08-07 07:57 UTCVendor advisory
- 2026-08-07 07:57 UTCGHSA enrichment
- 2026-08-06 19:55 UTCEG score recompute
- 2026-08-06 19:55 UTCVendor advisory
- 2026-08-06 19:55 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 07:53 UTCEG score recompute
- 2026-08-06 07:53 UTCVendor advisory
- 2026-08-06 07:53 UTCGHSA enrichment
- 2026-08-05 19:51 UTCEG score recompute▲ 1.00
- 2026-08-05 19:51 UTCVendor advisory
- 2026-08-05 19:51 UTCGHSA enrichment
- 2026-08-05 19:51 UTCNVD updateCVSS v3 → 8.1
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 08:02 UTCGHSA enrichment
- 2026-08-04 19:57 UTCEG score recompute
- 2026-08-04 19:57 UTCVendor advisory
- 2026-08-04 19:57 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 07:55 UTCVendor advisory
- 2026-08-04 07:54 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-12932?
When was CVE-2026-12932 disclosed?
Is CVE-2026-12932 actively exploited?
What is the CVSS score of CVE-2026-12932?
How do I remediate CVE-2026-12932?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12932
Is Your Infrastructure Affected by CVE-2026-12932?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.