CVE-2026-6679: wolfSSL DTLS 1.3 Heap Buffer Overflow DoS Vulnerability

Technical summary

CVE-2026-6679 is a heap buffer overflow in wolfSSL's DTLS 1.3 ACK serialization logic. An integer truncation during record-number list length computation causes undersized heap buffer allocation. Subsequent writes to the buffer overflow its bounds, corrupting heap metadata and adjacent allocations. The vulnerability is reachable in the pre-authentication phase of the DTLS handshake, requiring no credentials or peer validation. The flaw affects wolfSSL versions 5.9.0 and earlier; version 5.9.1 includes the fix.

Business impact

Systems running vulnerable wolfSSL versions handling DTLS 1.3 connections face denial-of-service risk. Each unauthenticated connection attempt can trigger a crash, enabling attackers to degrade availability without authentication or rate-limit bypass. Organizations relying on DTLS 1.3 for IoT, VPN, or real-time communication protocols face service interruption and potential cascading failures in multi-tier deployments. Recovery requires restart, and sustained attacks compound operational overhead.

Affected systems

wolfSSL versions 5.9.0 and earlier are vulnerable when compiled with DTLS 1.3 support enabled. Any application, firmware, or library build incorporating wolfSSL with DTLS 1.3 is at risk. This includes embedded systems, IoT devices, VPN appliances, and middleware that bundle wolfSSL for TLS/DTLS functionality. Organizations should audit their software bill of materials (SBOM) to identify direct and transitive dependencies on wolfSSL.

Exploitability

Exploitability is straightforward: an attacker sends a specially crafted DTLS 1.3 initial handshake packet that triggers ACK serialization before authentication. No vulnerability-specific tools, credentials, or user interaction are required. The attack is network-accessible (CVSS vector AV:N) and requires only basic network connectivity to the listening DTLS service. The lack of authentication requirement (PR:N) significantly lowers the bar for exploitation. Proof-of-concept code has not been disclosed in public sources as of the advisory date.

Remediation

Upgrade wolfSSL to version 5.9.1 or later. Organizations unable to upgrade immediately should implement network segmentation to restrict DTLS 1.3 listener exposure to trusted networks, disable DTLS 1.3 if not operationally required, and configure connection rate-limiting and per-peer connection quotas to mitigate repeated crash attempts.

Patch guidance

Apply wolfSSL 5.9.1 or later via your package manager, vendor update mechanism, or source rebuild as applicable. Verify the patched version is in use by checking library signatures or running version detection queries against deployed binaries. For embedded/firmware deployments, contact your device manufacturer or firmware provider for updated images. If wolfSSL is statically linked, rebuild affected applications with the patched library version. Prioritize patches for internet-facing DTLS listeners and production systems first.

Detection guidance

Monitor for repeated incoming DTLS 1.3 handshake attempts from single or distributed sources that correlate with service crashes or restarts. Enable verbose logging in wolfSSL (if available in your build) to capture ACK serialization events. Look for heap corruption signatures in crash logs (segmentation faults in memory allocator, heap invariant violations). Network-level detection is challenging but can flag unusual DTLS handshake packet patterns or connection floods to DTLS ports. Endpoint monitoring should track unexpected process terminations of services using DTLS 1.3.

Why prioritize this

This vulnerability merits immediate attention despite the denial-of-service-only impact (no code execution) because: (1) it requires no authentication or user interaction, (2) it affects a commonly embedded cryptography library in IoT and edge devices, (3) confirmed exploitation is trivial, and (4) many organizations are unaware of their wolfSSL dependency. Although not currently tracked in CISA's Known Exploited Vulnerabilities catalog, the simplicity of the attack and the library's ubiquity in supply chains make rapid patching essential to prevent coordinated availability attacks.

Risk score, explained

CVSS 3.1 score of 7.5 (HIGH) reflects high network accessibility and low attack complexity balanced against availability-only impact (no confidentiality or integrity breach). The unauthenticated attack vector and negligible privilege requirement elevate severity beyond typical DoS flaws. However, the absence of information disclosure or integrity violation prevents a CRITICAL rating. Organizations with DTLS 1.3 in production or critical-path infrastructure should treat this as HIGH priority; those with DTLS 1.3 only in optional or non-critical roles may accept lower patch urgency pending capacity assessment.

Frequently asked questions