CVE-2026-55215

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(low)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (8)

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

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

https://jira.mariadb.org/browse/CONJS-349
github Patch Available

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 20:24 UTCEG score recompute
  3. 2026-08-28 19:10 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55215?
CVE-2026-55215 is a high vulnerability 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 CVE-2026-55215 disclosed?
CVE-2026-55215 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55215 actively exploited?
CVE-2026-55215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55215?
CVE-2026-55215 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs