ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107384

MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)

Published Oct 8, 2026 · catalog updated Oct 16, 2026 · MariaDB Connector/Node.js: SQL injection

Check if you run it

No confirmed exploitation is on record for CVE-2026-107384. EPSS is 0.45%. Act only if a listed version of MariaDB Connector/Node.js: SQL injection is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (MariaDB Connector/Node.js: SQL injection).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.45%
Remediation
Advisory link
Affected products
npm mariadb

### Description With the non-default permitSetMultiParamEntries option enabled, an object passed as a query parameter is expanded into a SET clause, each key becoming a column name. The three code paths implementing that expansion built the backtick-quoted identifier by hand and wrote the key out unescaped, while only the value was escaped. A key containing a backtick therefore closed the identifier, and the remainder of the key was parsed as SQL. The connector's own identifier escaper (escapeId, which correctly doubles backticks) existed but was not called from any of the three sites. This is an incomplete fix of GitHub issue #252, which corrected escapeId itself in 2023 but left these hand-built call sites unchanged. ### Impact An application that enables permitSetMultiParamEntries and passes an object with attacker-influenced keys into a statement such as conn.query('UPDATE users SET ? WHERE id = ?', [body, id]) allows the caller to write columns the application never intended to expose — a role, balance or password column — and to append arbitrary SQL to the statement, since the injected text is not confined to an assignment. Exposure requires the option to be enabled: it is off by default, and with it off the object is serialised and escaped as a single string literal, so the key never reaches the SQL grammar. Passing a request body into this API is, however, the ordinary reason to enable the option. An application that enables it is asking for keys to become column names, not for keys to become arbitrary SQL. ### Resolution All three expansion sites now route the key through the identifier escaper, doubling backticks before writing the column name. The feature is unchanged for legitimate keys, including reserved words. ### Workarounds Disable permitSetMultiParamEntries (the default), or validate object keys against an allow-list of column names before passing them to query(), until upgraded. ### Credit Reported by fg0x0.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm mariadb3.2.0 → 3.2.5
  • npm mariadb3.3.0 → 3.3.4
  • npm mariadb3.4.0 → 3.4.7
  • npm mariadb3.5.0-rc.0 → 3.5.4

How to fix CVE-2026-107384

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107384. EPSS is 0.45%. Act only if a listed version of MariaDB Connector/Node.js: SQL injection is installed.

Which versions are affected?

Compare what you have installed with 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. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-89: SQL Injection. EPSS 0.45%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · GitHub Advisory Database

    Detected

    ### Description With the non-default permitSetMultiParamEntries option enabled, an object passed as a query parameter is expanded into a SET clause, each key becoming a column name. The three code paths implementing that expansion built the backtick-quoted identifier by hand and wrote the key out unescaped, while only the value was escaped. A key containing a backtick therefore closed the identifi

  2. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    mariadb fixed in 3.2.5; mariadb fixed in 3.3.4; mariadb fixed in 3.4.7; mariadb fixed in 3.5.4

  3. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    mariadb fixed in 3.2.5

  4. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    mariadb fixed in 3.3.4

  5. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    mariadb fixed in 3.4.7

  6. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    mariadb fixed in 3.5.4

  7. Oct 16, 2026 · GitHub Advisory Database

    Updated

    ### Description With the non-default permitSetMultiParamEntries option enabled, an object passed as a query parameter is expanded into a SET clause, each key becoming a column name. The three code paths implementing that expansion built the backtick-quoted identifier by hand and wrote the key out unescaped, while only the value was escaped. A key containing a backtick therefore closed the identifi

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.