# CVE-2026-86047: MariaDB: Insufficient quoting in mariadb-dump and SHOW commands > A low-privileged attacker can inject SQL via crafted identifiers in SHOW commands or dumps, leading to code execution when the output is applied. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 16 Oct 2026 - **Updated:** 19 Oct 2026 - **Also known as:** BELL-CVE-2026-86047, BIT-mariadb-2026-86047, BIT-mariadb-min-2026-86047, BIT-mysql-client-2026-86047, DEBIAN-CVE-2026-86047, ECHO-64c6-8c5b-034a, GHSA-wxr3-wm3p-7w6p, ROOT-OS-DEBIAN-12-CVE-2026-86047, ROOT-OS-DEBIAN-13-CVE-2026-86047, UBUNTU-CVE-2026-86047 ## What is CVE-2026-86047? CVE-2026-86047 is a high-severity SQL injection vulnerability in Mariadb Mariadb, published on 16 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, SHOW CREATE SERVER, SHOW CREATE USER, and mariadb-dump are affected because each does not consistently quote identifiers and values when serializing SQL. A low-privileged attacker can trigger the issue when an attacker-created object with crafted identifiers or values is included in SHOW output or a dump, then create an object with crafted identifiers or values so generated SQL contains injected statements and execute attacker-injected SQL when the poisoned output is applied. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2. Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) ## Which versions are affected by CVE-2026-86047? 3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mariadb` | Bitnami | From 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 | | `mariadb-min` | Bitnami | From 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 | | `mysql-client` | Bitnami | From 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 | Products: Mariadb Mariadb. ## How do I fix CVE-2026-86047? Upgrade mariadb to a fixed version for your release line: 10.6.28, 10.11.19, 11.4.13 or 11.8.9. ## Is CVE-2026-86047 being exploited? There is no known exploitation of CVE-2026-86047 in the wild and no public exploit code. ## Other vulnerabilities in Mariadb Mariadb - [CVE-2026-49261](https://insights.sbomify.com/CVE-2026-49261/): MariaDB server has unsafe parameter handling in `wsrep_notify_cmd` (critical 10.0) - [CVE-2026-85746](https://insights.sbomify.com/CVE-2026-85746/): MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections (critical 9.9) - [CVE-2026-85748](https://insights.sbomify.com/CVE-2026-85748/): MariaDB: Use-after-free with a large number of SYS_REFCURSOR's (critical 9.9) - [CVE-2026-92262](https://insights.sbomify.com/CVE-2026-92262/): MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. (critical 9.9) - [CVE-2023-26785](https://insights.sbomify.com/CVE-2023-26785/): Code injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-86047 and fix it if it is affected. What it is: CVE-2026-86047 is a high-severity SQL injection vulnerability in Mariadb Mariadb, published on 16 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-86047 in the wild and no public exploit code. Affected packages and fixed versions: - mariadb (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 - mariadb-min (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 - mysql-client (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 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-86047/ (Markdown: https://insights.sbomify.com/CVE-2026-86047/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86047 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86047 - OSV: https://osv.dev/vulnerability/CVE-2026-86047 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-86047/ Summaries are generated and may contain mistakes; the official description above is the record.