Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107384 high CVSS 8.1

SQL Injection in mariadb (CVE-2026-107384)

Summary

SQL injection in mariadb (CVE-2026-107384). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.5.4 or later.

Original description

The description as published by the source.

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…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107384 has been found in mariadb.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade mariadb to 3.5.4 or later.
If unsure, ask your IT team or search "mariadb CVE-2026-107384" on the vendor's site.

CVE-2026-107384 (mariadb) — CWE-89 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.5.4 — apply immediately
Workaround: Disable permitSetMultiParamEntries (the default), or validate object keys against an allow-list of column names before passing them to query(), until upgraded.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in mariadb.

📍 Affected scope

Check the vendor advisory for the affected versions of mariadb.

🔥 Severity

Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.5.4.

🛡️ Workaround

Workaround: Disable permitSetMultiParamEntries (the default), or validate object keys against an allow-list of column names before passing them to query(), until upgraded.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'mariadb' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mariadb を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Disable permitSetMultiParamEntries (the default), or validate object keys against an allow-list of column names before passing them to query(), until upgraded.

    パッチが適用されるまでの応急処置として、Disable permitSetMultiParamEntries (the default), or validate object keys against an allow-list of column names before passing them to query(), until upgraded. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade mariadb to 3.5.4

    ステージング環境で 3.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm mariadb
[{"type":"SEMVER","events":[{"introduced":"3.5.0-rc.0"},{"fixed":"3.5.4"}]}]
Bitnami mariadb
[{"type":"SEMVER","events":[{"introduced":"3.2.0"},{"fixed":"3.2.5"},{"introduced":"3.3.0"},{"fixed":"3.3.4"},{"introduced":"3.4.0"},{"fixed":"3.4.7"},{"introduced":"3.5.0"},{"fixed":"3.5.4"}]}]
Bitnami mariadb-min
[{"type":"SEMVER","events":[{"introduced":"3.2.0"},{"fixed":"3.2.5"},{"introduced":"3.3.0"},{"fixed":"3.3.4"},{"introduced":"3.4.0"},{"fixed":"3.4.7"},{"introduced":"3.5.0"},{"fixed":"3.5.4"}]}]
Bitnami mysql-client
[{"type":"SEMVER","events":[{"introduced":"3.2.0"},{"fixed":"3.2.5"},{"introduced":"3.3.0"},{"fixed":"3.3.4"},{"introduced":"3.4.0"},{"fixed":"3.4.7"},{"introduced":"3.5.0"},{"fixed":"3.5.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details