In all builds that make use of (D)TLS, including default builds, there is a series of conditional states during the TLS shutdown which could lead to a heap-use-after free. If an application ended up getting a partial wolfSSL_read() which is sometimes caused by a small user buffer passed in, then called wolfSSL_shutdown for a bidirectional close and attempted to wolfSSL_read() again while the peer continues trying to send data during the shutdown it would lead to a state where a potential heap-use-after free happened.
References
| Link | Resource |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/10863 | Issue Tracking |
Configurations
History
02 Oct 2026, 18:58
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.3 |
| First Time |
Wolfssl wolfssl
Wolfssl |
|
| CPE | cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:* | |
| References | () https://github.com/wolfSSL/wolfssl/pull/10863 - Issue Tracking |
27 Sep 2026, 10:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-27 10:16
Updated : 2026-10-02 18:58
NVD link : CVE-2026-15442
Mitre link : CVE-2026-15442
CVE.ORG link : CVE-2026-15442
JSON object : View
Products Affected
wolfssl
- wolfssl
CWE
CWE-416
Use After Free
