CVE-2026-15442

Heap use-after-free on read during bidirectional (D)TLS shutdown

MEDIUM
5.3
CVSS Score
Published: September 27, 2026 at 09:24 AM UTC
Updated: October 2, 2026 at 06:58 PM UTC
1 product affected across 1 vendorwolfSSL

Using wolfSSL by wolfSSL?

Get instant alerts when new vulnerabilities affect wolfSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4.0 ≤ v ≤ 5.9.24.4.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

Issue Tracking
Source: cverecord
https://github.com/wolfSSL/wolfssl/pull/10863

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card