CVE-2026-86047 — MariaDB: Insufficient quoting in mariadb-dump and SHOW commands
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (MariaDB Server).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.7 | CVSS 3.1 | High | 1.3 | 5.8 | security-advisories@github.com via NIST National Vulnerability Database |
| 7.7 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Source status changed · Published → Received
- Record published
- CVSS changed · 7.7
- Source status changed · → Published
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 16, 2026 – Oct 16, 2026
References
17 on the record
- jira.mariadb.org/browse/MDEV-39776
- github.com/MariaDB/server/releases/tag/mariadb-10.11.19
- github.com/MariaDB/server/commit/5acb43522863c9bd6b91f354104ea247bf513e9a
- github.com/MariaDB/server/commit/2b28d1c424104429eeed43115ee6d8a803671d52
- github.com/MariaDB/server/commit/9d4ffe23b25808f7858b2dc48106fbd60cf0e513
- github.com/MariaDB/server/commit/3646569225758c8225e7342783d775ef7c7570e5
- github.com/MariaDB/server/security/advisories/GHSA-wxr3-wm3p-7w6p
- github.com/MariaDB/server/commit/d5d741a3076f911b468518d6b06a917593498c5b
- jira.mariadb.org/browse/MDEV-40312
- jira.mariadb.org/browse/MDEV-40308
- jira.mariadb.org/browse/MDEV-39818
- github.com/MariaDB/server/releases/tag/mariadb-13.0.2
- github.com/MariaDB/server/releases/tag/mariadb-11.8.9
- github.com/MariaDB/server/releases/tag/mariadb-10.6.28
- jira.mariadb.org/browse/MDEV-40311
- github.com/MariaDB/server/releases/tag/mariadb-11.4.13
- github.com/MariaDB/server/releases/tag/mariadb-12.3.3
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-97380 MariaDB: GRANT PROXY with empty password incorrectly checks grantor's privileges 7h
- Critical CVE-2026-92262 MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. 7h
- Critical CVE-2026-85748 MariaDB: Use-after-free with a large number of SYS_REFCURSOR's 7h
- Medium CVE-2026-85745 MariaDB: Out-of-bound buffer read on in `ST_Area` of a multipolygon. 7h
- Critical CVE-2026-85746 MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections 7h
- Medium CVE-2026-85985 MariaDB: Unauthorized file access via CONNECT engine UDFs 7h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-86047 is "MariaDB: Insufficient quoting in mariadb-dump and SHOW commands", rated High. It affects Server (MariaDB); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.7 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.