# CVE-2026-107384: MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)

> Attackers can inject SQL via object keys in MariaDB Node.js connector when permitSetMultiParamEntries is enabled, allowing unauthorized data modification or code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** BIT-mariadb-2026-107384, BIT-mariadb-min-2026-107384, BIT-mysql-client-2026-107384, GHSA-v6pj-gxxw-phfw

## What is CVE-2026-107384?

CVE-2026-107384 is a high-severity SQL injection vulnerability in mariadb-corporation mariadb-connector-nodejs, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. From 3.2.0 until 3.2.5, 3.3.4, 3.4.7, and 3.5.4, applications that enable permitSetMultiParamEntries can pass objects whose keys are expanded into a SQL SET clause without being processed by escapeId. An attacker-controlled key containing a backtick can close the quoted identifier and cause the remainder of the key to be interpreted as SQL. This can update columns the application did not intend to expose and can append arbitrary SQL with the database user's privileges. The option is disabled by default, and serialized-object handling used when it is disabled is not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-107384?

11 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | From 3.2.0 | 3.2.5, 3.3.4, 3.4.7, 3.5.4 |
| `mariadb` | npm | From 3.2.0 | 3.2.5 |
| `mariadb` | npm | From 3.2.0 | 3.2.5 |
| `mariadb` | npm | From 3.3.0 | 3.3.4 |
| `mariadb` | npm | From 3.3.0 | 3.3.4 |
| `mariadb` | npm | From 3.4.0 | 3.4.7 |
| `mariadb` | npm | From 3.4.0 | 3.4.7 |
| `mariadb` | npm | From 3.5.0-rc.0 | 3.5.4 |
| `mariadb` | npm | From 3.5.0-rc.0 | 3.5.4 |
| `mariadb-min` | Bitnami | From 3.2.0 | 3.2.5, 3.3.4, 3.4.7, 3.5.4 |
| `mysql-client` | Bitnami | From 3.2.0 | 3.2.5, 3.3.4, 3.4.7, 3.5.4 |

## How do I fix CVE-2026-107384?

Upgrade mariadb to a fixed version for your release line: 3.2.5, 3.3.4, 3.4.7 or 3.5.4.

## Is CVE-2026-107384 being exploited?

There is no known exploitation of CVE-2026-107384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107384 and fix it if it is affected.

What it is: CVE-2026-107384 is a high-severity SQL injection vulnerability in mariadb-corporation mariadb-connector-nodejs, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107384 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected from 3.2.0; fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4
- mariadb (npm): affected from 3.2.0; fixed in 3.2.5
- mariadb (npm): affected from 3.2.0; fixed in 3.2.5
- mariadb (npm): affected from 3.3.0; fixed in 3.3.4
- mariadb (npm): affected from 3.3.0; fixed in 3.3.4
- mariadb (npm): affected from 3.4.0; fixed in 3.4.7
- mariadb (npm): affected from 3.4.0; fixed in 3.4.7
- mariadb (npm): affected from 3.5.0-rc.0; fixed in 3.5.4
- mariadb (npm): affected from 3.5.0-rc.0; fixed in 3.5.4
- mariadb-min (Bitnami): affected from 3.2.0; fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4
- mysql-client (Bitnami): affected from 3.2.0; fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107384/ (Markdown: https://insights.sbomify.com/CVE-2026-107384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107384
- OSV: https://osv.dev/vulnerability/CVE-2026-107384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107384/
Summaries are generated and may contain mistakes; the official description above is the record.