Skip to main content
Mallory
CriticalVulnerability

CVE-2024-1305: Kernel Buffer Overflow in tap-windows6 Driver

Published Jul 8, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS15.4%97th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenVPN
IdentifiersCVE-2024-1305CWE-787

CVE-2024-1305 is a memory corruption vulnerability in the Windows tap-windows6 driver version 9.26 and earlier. The flaw is caused by improper validation of size-related data for incoming write operations, specifically involving the PacketLength and PrefixLength parameters in the TapDeviceWrite method. By supplying crafted input that is not correctly bounds-checked, an attacker can trigger a buffer overflow in kernel context. The vulnerability can lead to a system bug check and, under favorable conditions, arbitrary code execution in kernel space.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause denial of service through a Windows bug check and may also permit arbitrary code execution in kernel mode. Kernel-level execution would give an attacker highly privileged control over the affected system, enabling full system compromise, security control bypass, and follow-on privilege escalation or persistence activities.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, reduce exposure by limiting who can interact with the vulnerable OpenVPN/TAP driver path, restricting use of affected Windows OpenVPN installations, and minimizing opportunities for untrusted data to reach the driver through OpenVPN sessions. Monitor affected systems for crashes and anomalous behavior associated with driver misuse. Where operationally feasible, disable or remove vulnerable OpenVPN/TAP components from systems that do not require them.

Remediation

Patch, then assume compromise.

Upgrade to a fixed OpenVPN/tap-windows6 release. The available information indicates that OpenVPN addressed the broader set of related vulnerabilities in version 2.6.10 and later; affected environments should ensure the bundled tap-windows6 driver is updated beyond version 9.26. Validate that all deployed Windows endpoints using OpenVPN have received the corrected driver package.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenVPNOpenvpn-Guiapplication
OpenVPNTap Windows6application
FAQ

Frequently asked questions

Is CVE-2024-1305 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2024-1305 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-1305?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-1305.
Is there a patch for CVE-2024-1305?
Upgrade to a fixed OpenVPN/tap-windows6 release. The available information indicates that OpenVPN addressed the broader set of related vulnerabilities in version 2.6.10 and later; affected environments should ensure the bundled tap-windows6 driver is updated beyond version 9.26.
What products are affected by CVE-2024-1305?
Openvpn-Gui and OpenVPN Tap Windows6.
How severe is CVE-2024-1305?
CVE-2024-1305 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 15.4% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.