Answer in brief
CVE-2026-107384 records a High severity (CVSS 8.1) vulnerability in MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries). The current sources do not mark it as known exploited. The current feed maps mariadb-corporation/mariadb-connector-nodejs (generic), mariadb (npm), mariadb (npm), mariadb (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mariadb-corporation/mariadb-connector-nodejs (generic), mariadb (npm), mariadb (npm), mariadb (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| mariadb-corporation/mariadb-connector-nodejsgeneric | >=3.2.0 <3.2.5 || >=3.3.0 <3.3.4 || >=3.4.0 <3.4.7 || >=3.5.0-rc.0 <3.5.4 | 3.2.5, 3.3.4, 3.4.7, 3.5.4 |
| mariadbnpm | >=3.2.0,<3.2.5 | 3.2.5 |
| mariadbnpm | >=3.3.0,<3.3.4 | 3.3.4 |
| mariadbnpm | >=3.4.0,<3.4.7 | 3.4.7 |
| mariadbnpm | >=3.5.0-rc.0,<3.5.4 | 3.5.4 |
Published upstream
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.