CVE-2026-107382

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

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

Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-10-08. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-95141 (ENISA EUVD) · GHSA-cx2f-j9fh-8g68 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. From 3.3.0 until 3.5.4, the zero-configuration TLS fingerprint-validation path calls Ed25519PasswordAuth.hash() through Authentication.validateFingerPrint, but Ed25519PasswordAuth.hash() references a seed identifier that is not in scope. Exposure requires a MariaDB server reached over TCP, TLS enabled with ssl: true or an ssl object whose rejectUnauthorized value is not false, a password set, no ssl.ca configured, and client_ed25519 negotiated as the authentication plugin. Under those conditions, a legitimate server, malicious server, or network attacker presenting a self-signed certificate can reach this path and cause a synchronous ReferenceError to escape the socket data handler. Under Node.js default uncaught-exception behavior, the client process terminates, causing denial of service. Configurations using a provided CA, rejectUnauthorized: false, another authentication plugin, or a Unix socket do not reach this vulnerable path. This issue is fixed in version 3.5.4.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
27
EG Risk 27/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)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 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
14th
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.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 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-31). 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

October 8, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Oct 8, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

[CONJS-356] Authentication / ed25519 plugin - Jira

https://jira.mariadb.org/browse/CONJS-356
GitHub release Patch Available

MariaDB Connector/Node.js 3.5.4

Patch available: mariadb-corporation/mariadb-connector-nodejs 3.5.4

https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4
GitHub commit Patch Available

commit 784ca3d75719 (mariadb-corporation/mariadb-connector-nodejs)

Patch available: mariadb-corporation/mariadb-connector-nodejs 3.5.4 (contains commit 784ca3d75719)

https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/784ca3d757194a05f202d84b0c762321e76a7915
GitHub advisoryMentions a patch (unverified)

Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS · Advisory · mariadb-corporation/mariadb-connector-nodejs · GitHub

Affected: 3.5.4. The 3.3.x and 3.4.x maintenance branches are not patched; upgrade to 3.5.4

https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cx2f-j9fh-8g68

Vendor Advisories for CVE-2026-107382(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmmariadb @ 3.5.4 (fixes >= 3.3.0, < 3.5.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 3.3.0 up to 3.5.4: fixed in 3.5.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-cx2f-j9fh-8g68 · GitHub severity MODERATE · GitHub CVSS 5.9
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-31 11:25 UTCOSV refresh
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-25 14:54 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-23 08:44 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-10-18 05:07 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 13 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-12 16:38 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-11 20:14 UTCEG score recompute
  5. 2026-10-11 18:26 UTCEG score recompute
  6. 2026-10-11 15:00 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-09 20:06 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-08 19:18 UTCEG score recompute
  12. 2026-10-08 18:37 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  13. 2026-10-08 18:37 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107382?
CVE-2026-107382 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. From 3.3.0 until 3.5.4, the zero-configuration TLS fingerprint-validation path calls Ed25519PasswordAuth.hash() through Authentication.validateFingerPrint, but Ed25519PasswordAuth.hash()…
When was the CVE record for CVE-2026-107382 published?
The CVE record for CVE-2026-107382 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-107382 actively exploited?
CVE-2026-107382 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107382?
CVE-2026-107382 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107382?
A fix for CVE-2026-107382 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107382 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-107382

Explore →

Is Your Infrastructure Affected by CVE-2026-107382?

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

Book a Demo →Browse All CVEs