CVE-2026-55215

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: 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. Prior to versions 3.3.3, 3.4.6, and 3.5.3, when ssl is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js sends credentials before completing certificate fingerprint validation. In lib/cmd/handshake/auth/handshake.js, a server that selects mysql_clear_password as the initial authentication plugin can receive the password before the post-TLS identity check. In lib/cmd/handshake/authentication.js, an authentication switch can evaluate the previous plugin instead of the requested target plugin, allowing mysql_clear_password to send the credential first. An active man-in-the-middle can present a self-signed certificate, capture the database password, and use it to authenticate directly even though the connector later rejects the server and closes the connection. This issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 28, 2026

Last Modified

September 8, 2026

Advisory Details (8)

Auto-updated Aug 28, 2026
Patch available. Sources: github_release, github, github_commit.
Web page

[CONJS-349] Cleartext password disclosure to MitM via mysql_clear_password - Jira

https://jira.mariadb.org/browse/CONJS-349
GitHub advisoryMentions a patch (unverified)

Connector leaks the cleartext password to an MitM despite `ssl: true` · Advisory · mariadb-corporation/mariadb-connector-nodejs · GitHub

Affected: 3.2.4, 3.3.3, 3.4.6, and 3.5.3. Upgrade to one of these (or later)

https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cqhc-2h57-wpxf
GitHub release Patch Available

MariaDB Connector/Node.js 3.5.3

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

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

MariaDB Connector/Node.js 3.4.6

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

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

MariaDB Connector/Node.js 3.3.3

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

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

commit ecd36958e6e3 (mariadb-corporation/mariadb-connector-nodejs)

Patch available: mariadb-corporation/mariadb-connector-nodejs 3.3.3 (contains commit ecd36958e6e3)

https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/ecd36958e6e3bf0e0fa8389546f50c0ed6dbb2ac
GitHub commit Patch Available

commit c47d7275835c (mariadb-corporation/mariadb-connector-nodejs)

Patch available: mariadb-corporation/mariadb-connector-nodejs 3.4.6 (contains commit c47d7275835c)

https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/c47d7275835c78c7eb8186cd23e9d57c045c128b
GitHub commit Patch Available

commit 514576a5a1fa (mariadb-corporation/mariadb-connector-nodejs)

Patch available: mariadb-corporation/mariadb-connector-nodejs 3.5.3 (contains commit 514576a5a1fa)

https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/514576a5a1fab3ea8498613e259a0b7a764e7302

Vendor Advisories for CVE-2026-55215(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 3.2.4: fixed in 3.2.4
  • 3.3.0 up to 3.3.3: fixed in 3.3.3
  • 3.4.0 up to 3.4.6: fixed in 3.4.6
  • 3.5.0 up to 3.5.3: fixed in 3.5.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 56× 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-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:17 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-10 00:49 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-09 02:37 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-08 00:50 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-07 03:03 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-06 00:47 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-05 08:44 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-03 15:12 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-03 01:57 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  25. 2026-10-01 22:31 UTCEG score recompute
Show 61 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-09-30 19:48 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-09-30 04:17 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-09-29 01:45 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-09-27 23:29 UTCEG score recompute
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-09-26 21:12 UTCEG score recompute
  11. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  12. 2026-09-26 08:03 UTCEG score recompute
  13. 2026-09-25 00:12 UTCEG score recompute
  14. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-09-23 21:49 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-09-22 19:34 UTCEG score recompute
  18. 2026-09-22 06:26 UTCEG score recompute
  19. 2026-09-21 03:38 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-20 01:22 UTCEG score recompute
  22. 2026-09-18 23:06 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-17 20:50 UTCEG score recompute
  25. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  26. 2026-09-17 03:13 UTCEG score recompute
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-09-16 14:05 UTCEG score recompute
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-15 11:23 UTCEG score recompute
  31. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-09-13 19:59 UTCEG score recompute
  33. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-09-12 17:34 UTCEG score recompute
  35. 2026-09-11 15:16 UTCEG score recompute
  36. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-09-10 13:01 UTCEG score recompute
  38. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-09-09 10:34 UTCEG score recompute
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-09-07 18:46 UTCEG score recompute
  42. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-09-06 16:28 UTCEG score recompute
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-09-06 03:18 UTCEG score recompute
  46. 2026-09-05 00:58 UTCEG score recompute
  47. 2026-09-04 11:51 UTCEG score recompute
  48. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-09-02 20:23 UTCEG score recompute
  50. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-09-01 15:34 UTCEG score recompute
  52. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-09-01 02:23 UTCEG score recompute
  55. 2026-09-01 02:10 UTCEG score recompute
  56. 2026-08-31 00:59 UTCEG score recompute
  57. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-08-30 11:51 UTCEG score recompute
  59. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-08-28 20:24 UTCEG score recompute
  61. 2026-08-28 19:10 UTCEG score recomputeFirst assessed: 7.5 HIGH

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55215?
CVE-2026-55215 is a high-severity vulnerability; its CVE record was published on August 28, 2026. MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to versions 3.3.3, 3.4.6, and 3.5.3, when ssl is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js sends credentials before completing certificate…
When was the CVE record for CVE-2026-55215 published?
The CVE record for CVE-2026-55215 was published on August 28, 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 September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-55215 actively exploited?
CVE-2026-55215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55215?
CVE-2026-55215 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55215?
A fix for CVE-2026-55215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55215 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-55215

Explore →

Is Your Infrastructure Affected by CVE-2026-55215?

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

Book a Demo →Browse All CVEs