Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-12932] Denial of Service due to memory leak in tls-crypt-v2 client key extraction

This high-severity Red Hat Linux advisory covers CVE-2026-12932.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-12932 Source published Jul 30, 2026Source updated Jul 30, 2026

VulniPulse record published Aug 1, 2026Record updated Aug 11, 2026

CVE-2026-12932

Affected products & platforms

Red Hat LinuxUnclassified

Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

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 A flaw was found in OpenVPN.

By sending a flood of specially crafted packets, an attacker can exhaust the system's memory, making the service unavailable. This vulnerability is rated as Important.

A memory leak within the tls-crypt-v2 client key extraction mechanism of OpenVPN can be remotely triggered by an unauthenticated attacker. This impact is significant due to the remote, unauthenticated nature of the attack.

Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-771.

Affected versions

2.5.0
2.6.20
2.7.4

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.