# MariaDB's connector leaks the cleartext password to an MitM despite \`ssl: true\`

Advisory record · `GHSA-cqhc-2h57-wpxf`

- **Identifiers:** `GHSA-cqhc-2h57-wpxf` · `BIT-mariadb-2026-55215` · `BIT-mariadb-min-2026-55215` · `BIT-mysql-client-2026-55215` · `CVE-2026-55215`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 28 Aug 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Aug 2026, 19:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mariadb` (npm): affected `<3.2.4 || >=3.3.0, <3.3.3 || >=3.4.0, <3.4.6 || >=3.5.0, <3.5.3`; fixed in `3.2.4`, `3.3.3`, `3.4.6`, `3.5.3`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 47th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 28 Aug 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-cqhc-2h57-wpxf](https://github.com/advisories/GHSA-cqhc-2h57-wpxf)
- [OSV: GHSA-cqhc-2h57-wpxf](https://osv.dev/vulnerability/GHSA-cqhc-2h57-wpxf)
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cqhc-2h57-wpxf>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/514576a5a1fab3ea8498613e259a0b7a764e7302>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/c47d7275835c78c7eb8186cd23e9d57c045c128b>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/ecd36958e6e3bf0e0fa8389546f50c0ed6dbb2ac>
- <https://hackerone.com/reports/3777370>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3>
- <https://jira.mariadb.org/browse/CONJS-349>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cqhc-2h57-wpxf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cqhc-2h57-wpxf/>. Everything for agents: <https://agentprime.io/llms.txt>.