CVE-2026-5264 is a heap buffer overflow in the wolfSSL embedded TLS library: a crafted DTLS 1.3 ACK message from the network writes past a heap buffer. NVD scores it 9.8 and wolfSSL rates it High. Only builds with DTLS 1.3, off by default, are affected; 5.9.1 fixes it, and stock OpenWrt builds do not enable DTLS 1.3.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
0.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-5264 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| wolfSSL (DTLS 1.3 ACK processing) | cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:* | NVD: before 5.9.1; only builds with DTLS 1.3 (--enable-dtls13 / WOLFSSL_DTLS13); fixed in 5.9.1 (PR 10076) |
| OpenWrt libwolfssl package | — | 5.7.6 in OpenWrt 24.10.0-24.10.6 and 5.8.4 in 25.12.0-25.12.2 (stock build has no --enable-dtls13); 5.9.1 from 24.10.7 and 25.12.3 |
What does this mean for affected devices?
CVE-2026-5264 is a heap-based buffer overflow (CWE-122, per wolfSSL as CNA) in wolfSSL's DTLS 1.3 code. The wolfSSL vulnerabilities page and the 5.9.1 section of the wolfSSL ChangeLog (8 April 2026) rate it High and describe it in one line: "A remote attacker can send a crafted DTLS 1.3 ACK message that triggers a heap buffer overflow." Sunwoo Lee and Seunghyun Yoon of the Korea Institute of Energy Technology (KENTECH) reported it, wolfSSL lists a time to fix of 1 day, and the fix is pull request 10076, "Dtls13: ack management improvements", merged on 31 March 2026.
NVD gives it a Primary CVSS v3.1 score of 9.8 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; wolfSSL's own CVSS v4.0 score is 8.3 and adds an attack requirement (AT:P) for the build condition. NVD's configuration covers wolfSSL up to (excluding) 5.9.1 (NVD). The GitHub advisory is GHSA-w5qh-hw7x-9w39.
The build condition is DTLS 1.3. wolfSSL's configure.ac lists --enable-dtls13 as "default: disabled", and the option is switched on by --enable-all. DTLS 1.3 is used by constrained devices that secure CoAP or other UDP traffic, so the exposure on a device is any DTLS 1.3 endpoint, client or server, that accepts packets from the network before or after the handshake.
OpenWrt is a firmware example with a public build record. Its libwolfssl package shipped 5.7.6 in OpenWrt 24.10.0 to 24.10.6 and 5.8.4 in 25.12.0 to 25.12.2, both inside NVD's range, and moved to 5.9.1 in 24.10.7 and 25.12.3 with the 5.9.1 update commit. The stock OpenWrt wolfSSL Makefile passes no --enable-dtls13 flag, and DTLS itself is an option whose Config.in default is n, so a stock OpenWrt build does not compile the vulnerable code; firmware that enables DTLS 1.3 on its own wolfSSL build does.
Debian fixed it in unstable with 5.9.1-0.1 and marks bookworm and trixie no-dsa (minor issue) (Debian security tracker). RTOS images that compile wolfSSL in with WOLFSSL_DTLS13 in user_settings.h need a rebuild against 5.9.1 or later.
CVE-2026-5264 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13), and FIRST EPSS gives it 0.0045, the 39.9th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
Check whether any wolfSSL build in the image defines DTLS 1.3, and move to 5.9.1 or later (the current release is 5.9.4). Our Mbed TLS and wolfSSL firmware guide covers finding the library and its build options, our memory corruption fix guide covers the weakness class, and our CoAP protocol security guide covers DTLS on constrained devices. The same 5.9.1 release fixed CVE-2026-5194 and CVE-2026-5188.
Evidence
- High; heap buffer overflow in DTLS 1.3 ACK processing via a crafted ACK; reported by Sunwoo Lee and Seunghyun Yoon (KENTECH); fixed in 5.9.1, PR 10076. — wolfSSL ChangeLog (5.9.1, 8 April 2026)
- High rating, time to fix 1 day, fixed in 5.9.1. — wolfSSL security vulnerabilities page
- NVD Primary CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); CNA CVSS v4.0 8.3 with AT:P; CPE range before 5.9.1; CWE-122 from the CNA. — NVD
- PR 10076 "Dtls13: ack management improvements" merged 2026-03-31. — GitHub
- --enable-dtls13 is default disabled; --enable-all turns it on. — wolfSSL configure.ac (v5.9.0-stable)
- OpenWrt wolfSSL configure arguments contain no dtls13 flag; DTLS is behind WOLFSSL_HAS_DTLS. — OpenWrt wolfSSL Makefile (v24.10.8)
- WOLFSSL_HAS_DTLS defaults to n. — OpenWrt wolfSSL Config.in (v25.12.6)
- OpenWrt libwolfssl 5.7.6 at v24.10.6, 5.9.1 at v24.10.7; 5.8.4 at v25.12.2, 5.9.1 at v25.12.3; update commit da8b65de. — OpenWrt
- Debian: fixed in unstable 5.9.1-0.1; bookworm and trixie no-dsa (minor issue). — Debian security tracker
- Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00454 (39.9th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories
Sources
- NVD
- wolfSSL: Security Vulnerabilities
- wolfSSL ChangeLog.md (release 5.9.1)
- wolfSSL pull request 10076: DTLS 1.3 ACK management
- GitHub Advisory GHSA-w5qh-hw7x-9w39
- wolfSSL configure.ac (v5.9.0-stable)
- OpenWrt commit: wolfssl update to 5.9.1
- OpenWrt wolfSSL package Makefile (v24.10.8)
- OpenWrt wolfSSL Config.in (v25.12.6)
- Debian security tracker
- CISA KEV
- FIRST EPSS
Frequently asked questions
Is every wolfSSL build affected by CVE-2026-5264?
No. The overflow is in DTLS 1.3 ACK processing, and wolfSSL's configure.ac lists --enable-dtls13 as disabled by default; --enable-all switches it on (per the wolfSSL ChangeLog and configure.ac).
Why is the NVD score 9.8 when wolfSSL rates it High?
NVD's CVSS v3.1 vector is network, low complexity, no privileges and full impact. wolfSSL's CVSS v4.0 score of 8.3 adds an attack requirement (AT:P) for the DTLS 1.3 build condition (per NVD).
Does OpenWrt build wolfSSL with DTLS 1.3?
No. The stock OpenWrt wolfSSL Makefile passes no --enable-dtls13 flag, and its DTLS option defaults to off; OpenWrt moved to wolfSSL 5.9.1 in 24.10.7 and 25.12.3 (per the OpenWrt Makefile, Config.in and package history).
Is CVE-2026-5264 in the CISA KEV catalog?
No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.0045, the 39.9th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?