Skip to main content
Mallory
HighVulnerability

CVE-2026-5264: Heap Buffer Overflow in wolfSSL DTLS 1.3 ACK Message Processing

Published Apr 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.3High · v4
EPSS0.45%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Wolfssl
IdentifiersCVE-2026-5264CWE-122 · Heap-based Buffer Overflow

CVE-2026-5264 is a high-severity heap-based buffer overflow in wolfSSL’s DTLS 1.3 ACK message processing. The flaw is triggered when the library processes a crafted DTLS 1.3 ACK message, causing memory to be written or handled beyond the bounds of an allocated heap buffer. The issue is remotely reachable over the network and affects deployments that support DTLS 1.3. Because the vulnerable condition occurs during protocol message handling, exploitation may be possible prior to peer authentication.

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 heap corruption, leading to remote process crashes and denial of service. Given the nature of heap buffer overflows in network-facing protocol parsers, the vulnerability may also create conditions for remote code execution, depending on the target build, memory layout, and exploitability characteristics of the affected environment.

Mitigation

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

If immediate patching is not possible, disable DTLS 1.3 support where operationally feasible, or restrict exposure of DTLS-enabled services to trusted networks and peers only. Reduce attack surface by limiting unauthenticated access to services using wolfSSL DTLS 1.3 and monitor for malformed or anomalous DTLS traffic targeting exposed endpoints. These measures only reduce exposure and do not eliminate the underlying flaw.

Remediation

Patch, then assume compromise.

Upgrade wolfSSL to a fixed release that includes the vendor’s correction for CVE-2026-5264, specifically wolfSSL 5.9.1 or later. Rebuild and redeploy affected applications and firmware images that embed vulnerable wolfSSL versions, especially on appliances, embedded devices, and DTLS-enabled services.

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
WolfsslWolfsslapplication
FAQ

Frequently asked questions

Is CVE-2026-5264 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5264 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5264?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5264.
Is there a patch for CVE-2026-5264?
Upgrade wolfSSL to a fixed release that includes the vendor’s correction for CVE-2026-5264, specifically wolfSSL 5.9.1 or later. Rebuild and redeploy affected applications and firmware images that embed vulnerable wolfSSL versions, especially on appliances, embedded devices, and DTLS-enabled services.
What products are affected by CVE-2026-5264?
Wolfssl.
How severe is CVE-2026-5264?
CVE-2026-5264 has a CVSS v4 score of 8.3 (High) and an EPSS score of 0.45% (40th percentile) as of Sep 25, 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 malwareMalware 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 activity3Community discussion across Reddit, Mastodon, and other social sources.