Heap use-after-free on read during bidirectional (D)TLS shutdown (CVE-2026-15442) | HOL Guard CVE

Low · CVSS 2.3CVE-2026-15442

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

Answer in brief

CVE-2026-15442 records a Low severity (CVSS 2.3) vulnerability in Heap use-after-free on read during bidirectional (D)TLS shutdown. The current sources do not mark it as known exploited. The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 27, 2026Updated Sep 27, 2026Source checked Sep 27, 2026First seen by HOL Sep 27, 2026Material review Sep 27, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 2.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
wolfSSL/wolfSSLgeneric	>=4.4.0 <=5.9.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for wolfSSL/wolfSSL.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 27, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.