# MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters

Advisory record · `GHSA-48qf-xh34-q73r`

- **Identifiers:** `GHSA-48qf-xh34-q73r` · `BIT-mariadb-2026-107383` · `BIT-mariadb-min-2026-107383` · `BIT-mysql-client-2026-107383` · `CVE-2026-107383`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 8 Oct 2026
- **Updated:** 16 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `mariadb` (npm): affected `<3.2.5 || >=3.3.0, <3.3.4 || >=3.4.0, <3.4.7 || >=3.5.0-rc.0, <3.5.4`; fixed in `3.2.5`, `3.3.4`, `3.4.7`, `3.5.4`

## 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.0039, the 33rd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-48qf-xh34-q73r)

## Sources

- [GitHub Advisory Database: GHSA-48qf-xh34-q73r](https://github.com/advisories/GHSA-48qf-xh34-q73r)
- [OSV: GHSA-48qf-xh34-q73r](https://osv.dev/vulnerability/GHSA-48qf-xh34-q73r)
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-48qf-xh34-q73r>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/2314c03b785db482599d2befd06f4992e5fc46b3>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/a4aa048b57dc47309b80e5cc25a4a8eedb32fd9f>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/b2ca628864b0fc2e3e94ea96910f6b693ad5bd30>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/faa27d1b2b7753a54000f586d5148089b60d1284>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.5>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.4>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.7>
- <https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4>
- <https://jira.mariadb.org/browse/CONJS-367>

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-48qf-xh34-q73r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-48qf-xh34-q73r/>. Everything for agents: <https://agentprime.io/llms.txt>.