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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap buffer overflow vulnerability in wolfSSL DTLS 1.3 ACK handling that may allow remote crashes or code execution.
A heap buffer overflow vulnerability in DTLS 1.3 ACK message processing that can be triggered remotely via a crafted ACK message.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.