CVE-2026-15442

MEDIUMNVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-09-27. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
24
EG Risk 24/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 27, 2026

Last Modified

October 2, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Fix use-after-free in some TLS shutdown/ReceiveData sequences

Fix merged in wolfSSL/wolfssl PR #10863 on 2026-07-08 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/10863

Vendor Advisories for CVE-2026-15442(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl5.5.4-2 ... 5.9.2-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl5.7.2-0.1 ... 5.9.2-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 15:28 UTCVendor advisory
  2. 2026-10-04 15:28 UTCGHSA enrichment
  3. 2026-10-03 17:14 UTCEG score recompute
  4. 2026-10-03 17:14 UTCVendor advisory
  5. 2026-10-03 17:14 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-02 19:00 UTCEG score recompute▲ 3.00
  8. 2026-10-02 19:00 UTCVendor advisory
  9. 2026-10-02 19:00 UTCGHSA enrichment
  10. 2026-10-02 18:59 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-30 11:19 UTCEG score recompute
  14. 2026-09-30 11:19 UTCGHSA enrichment
  15. 2026-09-30 10:55 UTCEG score recompute
  16. 2026-09-30 10:54 UTCGHSA enrichment
  17. 2026-09-29 15:20 UTCEPSS rescore
  18. 2026-09-28 20:50 UTCEG score recompute
  19. 2026-09-28 20:50 UTCGHSA enrichment
  20. 2026-09-28 13:51 UTCEPSS rescore
  21. 2026-09-27 13:47 UTCEPSS rescore
  22. 2026-09-27 10:20 UTCEG score recompute
  23. 2026-09-27 09:35 UTCEG score recompute
  24. 2026-09-27 09:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15442?
CVE-2026-15442 is a medium vulnerability published on September 27, 2026. 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 wolfSSLread() which is sometimes caused by a small user buffer passed in, then…
When was CVE-2026-15442 disclosed?
CVE-2026-15442 was first published on September 27, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15442 actively exploited?
CVE-2026-15442 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15442?
CVE-2026-15442 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-15442?
An upstream fix for CVE-2026-15442 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-15442 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15442

Explore →

Is Your Infrastructure Affected by CVE-2026-15442?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs