CVE-2026-94418

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: LOW) published 2026-09-27. NVD baseline CVSS 7.5; 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-87907 (ENISA EUVD) · GHSA-q4rg-xp99-jj6q (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak memory down, then merges the two results, but it merged the signature result back only when the parse returned 0, so any parse error hid it. ParseCertRelative() reaches its validity-date, name-constraint and critical-extension checks only after ConfirmSignature() has passed, so splitting the signature check out inverts the precedence that makes "override date errors" a sound policy, and ASN_SIG_CONFIRM_E is never surfaced anywhere. The attacker needs no key material from the real PKI and no CA compromise: a self-made certificate carrying the expected subject name, the trusted CA's subject as its issuer, arbitrary bytes where the signature goes, a validity window in the past and the attacker's own key pair is sufficient. Affected builds define WOLFSSL_SMALL_CERT_VERIFY, which is off by default, is not set implicitly by any platform or preset header, and is not reachable from any CMake option; the autotools routes are --enable-lowresource, --enable-leantls, --enable-tinytls13=cert and --enable-tinytls13=mutualauth, and examples/configs/user_settings_embedded.h reaches it through WC_CFG_SMALL_CERT_VERIFY, which ships as 0, while neither --enable-all nor --enable-distro enables it at all. The application must additionally install a verify callback through wolfSSL_CTX_set_verify() or wolfSSL_set_verify() with WOLFSSL_VERIFY_PEER that returns 1 for ASN_BEFORE_DATE_E or ASN_AFTER_DATE_E; wolfSSL ships this exact shape as myVerify() in wolfssl/test.h under VERIFY_OVERRIDE_DATE_ERR, which examples/client -D selects. An application with no callback, or whose callback returns preverify for date errors, still fails the handshake, and wolfSSL_CertManagerVerifyBuffer() and wc_CheckCertSignature() report ASN_SIG_CONFIRM_E correctly in the same binary. TLS 1.2 and TLS 1.3 are affected in both directions, and DTLS reaches the same function; where the forged certificate is a chain certificate the callback's consent causes it to be cached in the WOLFSSL_CTX certificate manager, so an exposed deployment must restart the context or the process rather than merely reconnect.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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

October 2, 2026

Advisory Details (1)

Auto-updated Oct 2, 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-94418(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 / 67× 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.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-94418?
CVE-2026-94418 is a high-severity vulnerability; its CVE record was published on September 27, 2026. Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak memory down, then merges the two results, but it merged the signature result back only when the parse returned 0, so any parse error hid it. ParseCertRelative()…
When was CVE-2026-94418 made public?
CVE-2026-94418 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-94418 actively exploited?
CVE-2026-94418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94418?
CVE-2026-94418 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-94418?
A fix for CVE-2026-94418 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94418 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-94418

Explore →

Is Your Infrastructure Affected by CVE-2026-94418?

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

Book a Demo →Browse All CVEs