---
id: CVE-2026-15442
title: >-
  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
summary: >-
  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…
severity: low
cvss: 2.3
cvssVector: 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'
cwe:
  - CWE-416
vendor: wolfSSL
product: wolfSSL
affected:
  - wolfSSL >= 4.4.0 <= 5.9.2
published: '2026-09-27'
updated: '2026-09-27'
sourceUpdated: '2026-09-27T10:16:56.893'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-15442'
references:
  - url: 'https://github.com/wolfSSL/wolfssl/pull/10863'
    label: facts@wolfssl.com
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-09-27T09:45:46.029Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.