Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/10863 |
|
Sun, 27 Sep 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wolfssl
Wolfssl wolfssl |
|
| Vendors & Products |
Wolfssl
Wolfssl wolfssl |
Sun, 27 Sep 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Heap use-after-free on read during bidirectional (D)TLS shutdown | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: wolfSSL
Published:
Updated: 2026-09-27T09:24:31.594Z
Reserved: 2026-07-10T19:09:12.486Z
Link: CVE-2026-15442
No data.
Status : Received
Published: 2026-09-27T10:16:56.893
Modified: 2026-09-27T10:16:56.893
Link: CVE-2026-15442
No data.
OpenCVE Enrichment
Updated: 2026-09-27T12:00:16Z