CVE-2026-94417

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-87908 (ENISA EUVD) · GHSA-vqr9-9vw2-33w6 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
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: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When an application enables both OCSP and CRL revocation checking on one WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer certificate that carries no Authority Information Access OCSP URL, and accepts a certificate the loaded CRL lists as revoked. The soft-fail policy for a missing responder collapses the OCSP result onto success before the code decides whether the CRL fallback is still needed, so "no responder exists" becomes indistinguishable from "the responder answered good". Affected builds define both HAVE_OCSP and HAVE_CRL: --enable-ocsp --enable-crl directly, and implicitly --enable-all, --enable-distro, --enable-curl, --enable-nginx, --enable-haproxy, --enable-stunnel, --enable-lighty, --enable-wpas, --enable-strongswan, --enable-mosquitto, --enable-jni, --enable-openvpn and --enable-krb. An application is affected only if it calls both wolfSSL_CTX_EnableOCSP() (or wolfSSL_EnableOCSP() / wolfSSL_CertManagerEnableOCSP()) and wolfSSL_CTX_EnableCRL() (or the equivalents) with a CRL loaded; an application that uses OCSP stapling alone through wolfSSL_CTX_EnableOCSPStapling() is not affected, because that sets up a separate OCSP instance. The defect sits in ProcessPeerCerts() and is reachable over TLS 1.0 through TLS 1.3 and DTLS, both on a client verifying a server certificate and on a server verifying a client certificate under mutual or post-handshake authentication. When the skipped check falls on a chain certificate rather than the leaf, the unchecked intermediate is promoted into the certificate manager and stays a trusted signer for every later connection on that context, so an affected long-running process needs its WOLFSSL_CTX torn down and not only its library replaced. All wolfSSL versions from 5.9.2 and earlier are affected; on versions 5.9.1 and 5.9.2 the WOLFSSL_OCSP_CHECKALL configuration fails closed with OCSP_NEED_URL, which leaves wolfSSL_CTX_EnableOCSP() without CHECKALL as the exposed configuration on 5.9.2.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium 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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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
6th
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.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-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-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 29, 2026

Advisory Details (1)

Auto-updated Sep 29, 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-94417(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 8× in last 7d / 68× 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 92 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-27 12:31 UTCEG score recompute
  7. 2026-10-27 12:31 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  8. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-25 13:49 UTCEG score recompute
  11. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-22 12:26 UTCEG score recompute
  15. 2026-10-22 12:26 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-18 02:58 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 66 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-12 14:42 UTCEG score recompute
  3. 2026-10-12 01:17 UTCVendor advisory
  4. 2026-10-12 01:17 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  5. 2026-10-11 19:12 UTCEG score recompute
  6. 2026-10-11 16:27 UTCEG score recompute
  7. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-11 13:40 UTCEG score recompute
  9. 2026-10-11 02:42 UTCEG score recompute
  10. 2026-10-11 02:42 UTCVendor advisory
  11. 2026-10-11 02:42 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-10 04:11 UTCEG score recompute
  14. 2026-10-10 04:11 UTCVendor advisory
  15. 2026-10-10 04:11 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  16. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-09 05:37 UTCEG score recompute
  18. 2026-10-09 05:37 UTCVendor advisory
  19. 2026-10-09 05:37 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  20. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-08 07:06 UTCEG score recompute
  22. 2026-10-08 07:06 UTCVendor advisory
  23. 2026-10-08 07:06 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-07 08:35 UTCEG score recompute
  26. 2026-10-07 08:35 UTCVendor advisory
  27. 2026-10-07 08:35 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  28. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-10-06 10:04 UTCEG score recompute
  30. 2026-10-06 10:04 UTCVendor advisory
  31. 2026-10-06 10:04 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  32. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-10-05 11:05 UTCEG score recompute
  34. 2026-10-05 11:05 UTCVendor advisory
  35. 2026-10-05 11:04 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  36. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-10-04 12:34 UTCEG score recompute
  38. 2026-10-04 12:34 UTCVendor advisory
  39. 2026-10-04 12:34 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  40. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-10-03 14:03 UTCEG score recompute
  42. 2026-10-03 14:03 UTCVendor advisory
  43. 2026-10-03 14:03 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  44. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-10-02 15:32 UTCEG score recompute
  46. 2026-10-02 15:32 UTCVendor advisory
  47. 2026-10-02 15:32 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  48. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-10-01 17:00 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  50. 2026-09-30 17:56 UTCEG score recompute
  51. 2026-09-30 17:56 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW · GitHub CVSS 5.3
  52. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-09-29 19:22 UTCEG score recompute▲ 3.00
  54. 2026-09-29 19:22 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW
  55. 2026-09-29 19:19 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  56. 2026-09-29 18:32 UTCEG score recompute
  57. 2026-09-29 18:32 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW
  58. 2026-09-29 17:58 UTCEG score recompute
  59. 2026-09-29 17:57 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW
  60. 2026-09-28 20:50 UTCEG score recompute
  61. 2026-09-28 20:50 UTCGHSA enrichmentGHSA-vqr9-9vw2-33w6 · GitHub severity LOW
  62. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  64. 2026-09-27 10:20 UTCEG score recompute
  65. 2026-09-27 09:20 UTCEG score recomputeFirst assessed: 2.3 LOW
  66. 2026-09-27 09:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-94417?
CVE-2026-94417 is a medium-severity vulnerability; its CVE record was published on September 27, 2026. When an application enables both OCSP and CRL revocation checking on one WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer certificate that carries no Authority Information Access OCSP URL, and accepts a certificate the loaded CRL lists as revoked. The soft-fail policy…
When was CVE-2026-94417 made public?
CVE-2026-94417 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-94417 actively exploited?
CVE-2026-94417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94417?
CVE-2026-94417 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-94417?
A fix for CVE-2026-94417 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94417 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-94417

Explore →

Is Your Infrastructure Affected by CVE-2026-94417?

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

Book a Demo →Browse All CVEs