Skip to main content
VulnerabilityPublished Updated

CVE-2026-15442: 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

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

AI-suggested

Until a fix is available, applications should avoid calling wolfSSL_read() after wolfSSL_shutdown during bidirectional shutdown sequences if the peer may still send data. Monitor vendor communications for updates and patches.

Description

CVE-2026-15442 is a heap-use-after-free vulnerability affecting all builds using (D)TLS, including default builds. It arises during the TLS shutdown process when certain conditional states occur. Specifically, if an application performs a partial wolfSSL_read() due to a small user buffer, then calls wolfSSL_shutdown for a bidirectional close, and attempts another wolfSSL_read() while the peer continues sending data, a heap-use-after-free condition may occur. This vulnerability has a CVSS score of 5.3, indicating a low severity impact primarily affecting availability.

References

Community reviews

Loading reviews…