CVE-2026-93304

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-87909 (ENISA EUVD) · GHSA-vpg5-xh2g-4x3c (GitHub Security Advisories)Source: ENISA EUVD

3.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A (D)TLS 1.2 client can accept a ChangeCipherSpec message before it has sent its ClientKeyExchange. No master secret has been derived at that point, so the client installs read keys derived from a known (deterministic) key and checks the server's Finished against that same key. An out-of-order ChangeCipherSpec can therefore be used by an attacker to complete the handshake in place of the server and send data the client accepts as authentic. The client's own traffic still uses correctly derived keys, so the attacker cannot read it, and the genuine server never completes the handshake. DTLS 1.2 clients are exposed because a datagram read can deliver the out-of-order records on its own. TLS 1.2 clients are exposed when the application supplies received bytes with wolfSSL_inject() or enables read ahead. For certificate suites, the attacker must be in a man-in-the-middle position. For PSK (Pre Shared Key) connections, any fake server can succeed without knowing the PSK.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
17
EG Risk 17/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 27, 2026

Last Modified

October 2, 2026

Advisory Details (1)

Auto-updated Sep 27, 2026
Patch available. Sources: github_pr.
GitHub pull request

Only process CCS after CKE is sent. Fix verification logic for RPK. Clear legacy_session_id when using TLS 1.3. Forbid Certificate messages for PSK.

Fix merged in wolfSSL/wolfssl PR #11458 on 2026-09-18 — awaiting tagged release

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

Vendor Advisories for CVE-2026-93304(2)

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

Affected Packages

(3 across 3 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • 4.7.0 up to 5.9.4-r0: fixed in 5.9.4-r0
—
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 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 84 is merged into the row it repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-11-07 19:07 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c · GitHub severity MODERATE · GitHub CVSS 3.7
  7. 2026-11-07 19:07 UTCEchelonGraph re-scored
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-27 12:31 UTCEchelonGraph re-scored
  21. 2026-10-27 12:31 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c · GitHub CVSS 3.7
  22. 2026-10-27 07:55 UTCOSV refresh
  23. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-25 13:49 UTCEchelonGraph re-scored
Show 58 more
  1. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-18 02:59 UTCEchelonGraph re-scored
  9. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-12 14:43 UTCEchelonGraph re-scored
  16. 2026-10-11 19:12 UTCEchelonGraph re-scored
  17. 2026-10-11 16:28 UTCEchelonGraph re-scored
  18. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-11 13:42 UTCEchelonGraph re-scored
  20. 2026-10-11 03:46 UTCEchelonGraph re-scored
  21. 2026-10-11 03:46 UTCVendor advisory
  22. 2026-10-11 03:46 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c · GitHub CVSS 3.7
  23. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-10-08 08:47 UTCEchelonGraph re-scored
  27. 2026-10-08 08:47 UTCVendor advisory
  28. 2026-10-08 08:47 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c · GitHub CVSS 3.7
  29. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-10-05 13:49 UTCEchelonGraph re-scored
  33. 2026-10-05 13:49 UTCVendor advisory
  34. 2026-10-05 13:49 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c · GitHub CVSS 3.7
  35. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-10-02 18:51 UTCEchelonGraph re-scored▼ 2.60
  37. 2026-10-02 18:51 UTCVendor advisory
  38. 2026-10-02 18:51 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  39. 2026-10-02 18:51 UTCNVD updateCVSS v3 → 3.7 · severity → LOW
  40. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-10-01 18:49 UTCVendor advisory
  42. 2026-10-01 18:49 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  43. 2026-09-30 18:14 UTCEchelonGraph re-scored
  44. 2026-09-30 18:13 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  45. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-09-29 17:36 UTCEchelonGraph re-scored
  47. 2026-09-29 17:36 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  48. 2026-09-29 16:54 UTCEchelonGraph re-scored
  49. 2026-09-29 16:54 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  50. 2026-09-28 20:50 UTCEchelonGraph re-scored
  51. 2026-09-28 20:50 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  52. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-09-28 10:55 UTCEchelonGraph re-scored
  54. 2026-09-28 10:55 UTCGHSA enrichmentGHSA-vpg5-xh2g-4x3c
  55. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-27 10:20 UTCEchelonGraph re-scored
  57. 2026-09-27 09:20 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
  58. 2026-09-27 09:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-93304?
CVE-2026-93304 is a low-severity vulnerability; its CVE record was published on September 27, 2026. A (D)TLS 1.2 client can accept a ChangeCipherSpec message before it has sent its ClientKeyExchange. No master secret has been derived at that point, so the client installs read keys derived from a known (deterministic) key and checks the server's Finished against that same key. An out-of-order…
When was CVE-2026-93304 made public?
CVE-2026-93304 was made public on September 26, 2026: that is the date its CVE record's CNA, wolfSSL Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
Is CVE-2026-93304 actively exploited?
CVE-2026-93304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93304?
CVE-2026-93304 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-93304?
A fix for CVE-2026-93304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-93304 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-93304

Explore →

Is Your Infrastructure Affected by CVE-2026-93304?

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

Book a Demo →Browse All CVEs