CVE-2026-94419

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-87906 (ENISA EUVD) · GHSA-c72q-45p9-v8qh (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
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.1%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Without NO_SESSION_CACHE_REF, wolfSSL_get_session() does not return a session object but a ClientSession reference of the form {row, index, hash(sessionID)} into the process-global SessionCache, and ClientSessionToSession() validates it against that hash alone. Because the TLS 1.2 session ID is chosen by the server and sent in clear, AddSessionToCache() matches any other server's session on the same ID and overwrites the client-side entry with that server's master secret, cipher suite and version, while the handle continues to resolve; nothing on the write path compares the peer, the application's server ID or the WOLFSSL_CTX. Resuming through the handle then produces an abbreviated handshake in which no Certificate message is sent, so neither chain verification nor wolfSSL_check_domain_name() runs, and the attacker is accepted as the original server for the whole of that connection. Affected builds are those leaving NO_SESSION_CACHE_REF, NO_SESSION_CACHE, NO_CLIENT_CACHE and TITAN_SESSION_CACHE all undefined, which includes a plain ./configure, --enable-opensslextra and --enable-opensslall; fifteen integration options define NO_SESSION_CACHE_REF and are therefore not affected, among them --enable-all, --enable-distro, --enable-curl, --enable-nginx, --enable-haproxy, --enable-stunnel, --enable-wpas and the rest of the OPENSSL_COMPATIBLE_DEFAULTS family, and --enable-leanpsk, --enable-leantls, --enable-lowresource and --enable-tinytls13 disable the cache outright. The application must use the legacy reference flow, wolfSSL_get_session() or SSL_get_session() followed by wolfSSL_set_session(); wolfSSL_get1_session() returns the session object itself and is not affected, nor are wolfSSL_SetServerID() lookups. Only TLS 1.2 and below and DTLS 1.2 and below are reachable, since TLS 1.3 and ticket resumption with an empty ServerHello session ID both use a client-chosen cache key. The poisoned entry lives in the process-global cache, so it crosses WOLFSSL_CTX boundaries and persists until the entry is evicted or the session times out, 500 seconds by default. Releases v5.3.0 through v5.9.2 are affected; the fix adds a per-write generation counter to the cache and raises WOLFSSL_CACHE_VERSION from 2 to 3, so a cache persisted by an older build is rejected by a fixed one.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 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.1%
EPSS %ILE
below the 1st
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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

September 30, 2026

Advisory Details (1)

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

Certificate verification and session cache hardening

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

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

Vendor Advisories for CVE-2026-94419(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 5× in last 7d / 52× 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 it from the CNA feed. 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). 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 73 is merged into the row it repeats.

  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  3. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  4. 2026-10-27 09:32 UTCEG score recompute
  5. 2026-10-27 09:32 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  7. 2026-10-25 13:49 UTCEG score recompute
  8. 2026-10-22 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-22 12:27 UTCEG score recompute
  10. 2026-10-22 12:26 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  11. 2026-10-21 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-10-20 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-18 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-18 02:58 UTCEG score recompute
  15. 2026-10-16 16:45 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-14 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-13 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-12 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-12 14:42 UTCEG score recompute
  20. 2026-10-11 19:12 UTCEG score recompute
  21. 2026-10-11 17:04 UTCVendor advisory
  22. 2026-10-11 17:04 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  23. 2026-10-11 16:27 UTCEG score recompute
  24. 2026-10-11 13:50 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-10-11 13:40 UTCEG score recompute
Show 47 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-10 17:21 UTCEG score recompute
  3. 2026-10-10 17:21 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  4. 2026-10-09 20:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-09 17:40 UTCEG score recompute
  6. 2026-10-09 17:40 UTCVendor advisory
  7. 2026-10-09 17:39 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  8. 2026-10-08 17:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-08 17:13 UTCEG score recompute
  10. 2026-10-08 17:13 UTCVendor advisory
  11. 2026-10-08 17:13 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-07 17:31 UTCVendor advisory
  14. 2026-10-07 17:31 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  15. 2026-10-06 15:53 UTCEG score recompute
  16. 2026-10-06 15:53 UTCVendor advisory
  17. 2026-10-06 15:53 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  18. 2026-10-06 15:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-05 17:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-10-05 16:12 UTCVendor advisory
  21. 2026-10-05 16:12 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  22. 2026-10-04 16:32 UTCVendor advisory
  23. 2026-10-04 16:32 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  24. 2026-10-03 16:50 UTCEG score recompute
  25. 2026-10-03 16:50 UTCVendor advisory
  26. 2026-10-03 16:50 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  27. 2026-10-03 14:26 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  28. 2026-10-02 17:09 UTCEG score recompute
  29. 2026-10-02 17:09 UTCVendor advisory
  30. 2026-10-02 17:09 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  31. 2026-10-01 19:51 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  32. 2026-10-01 17:28 UTCEG score recompute
  33. 2026-10-01 17:28 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW · GitHub CVSS 5.4
  34. 2026-09-30 17:47 UTCEG score recompute▲ 3.10
  35. 2026-09-30 17:47 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW
  36. 2026-09-30 17:44 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  37. 2026-09-29 17:37 UTCEG score recompute
  38. 2026-09-29 17:36 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW
  39. 2026-09-29 16:54 UTCEG score recompute
  40. 2026-09-29 16:54 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW
  41. 2026-09-28 20:50 UTCEG score recompute
  42. 2026-09-28 20:50 UTCGHSA enrichmentGHSA-c72q-45p9-v8qh · GitHub severity LOW
  43. 2026-09-28 13:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  44. 2026-09-27 13:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  45. 2026-09-27 09:20 UTCEG score recompute
  46. 2026-09-27 09:01 UTCEG score recomputeFirst assessed: 2.3 LOW
  47. 2026-09-27 09:00 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-94419?
CVE-2026-94419 is a medium-severity vulnerability; its CVE record was published on September 27, 2026. Without NO_SESSION_CACHE_REF, wolfSSL_get_session() does not return a session object but a ClientSession reference of the form {row, index, hash(sessionID)} into the process-global SessionCache, and ClientSessionToSession() validates it against that hash alone. Because the TLS 1.2 session ID is…
When was CVE-2026-94419 made public?
CVE-2026-94419 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-94419 actively exploited?
CVE-2026-94419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94419?
CVE-2026-94419 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-94419?
A fix for CVE-2026-94419 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94419 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-94419

Explore →

Is Your Infrastructure Affected by CVE-2026-94419?

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

Book a Demo →Browse All CVEs