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.
CVE-2026-86047
HIGHPre-NVD 7.77.7Trending — Patch released this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.7Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.7
- EG Score
- 7.7HIGHmedium confidence
- EG Risk
- 35EG Risk 35/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity77% × 45%Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 24th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 16, 2026
Last Modified
October 20, 2026
Advisory Details (10)
Auto-updated Oct 16, 2026Patch available. Sources: github_commit, github_release.
GitHub release Patch Available
MariaDB Community Server 12.3.3
Patch available: MariaDB/server mariadb-12.3.3
https://github.com/MariaDB/server/releases/tag/mariadb-12.3.3GitHub release Patch Available
MariaDB Community Server 11.8.9
Patch available: MariaDB/server mariadb-11.8.9
https://github.com/MariaDB/server/releases/tag/mariadb-11.8.9GitHub release Patch Available
MariaDB Community Server 11.4.13
Patch available: MariaDB/server mariadb-11.4.13
https://github.com/MariaDB/server/releases/tag/mariadb-11.4.13GitHub release Patch Available
MariaDB Community Server 10.6.28
Patch available: MariaDB/server mariadb-10.6.28
https://github.com/MariaDB/server/releases/tag/mariadb-10.6.28GitHub release Patch Available
MariaDB Community Server 10.11.19
Patch available: MariaDB/server mariadb-10.11.19
https://github.com/MariaDB/server/releases/tag/mariadb-10.11.19GitHub commit Patch Available
commit d5d741a3076f (MariaDB/server)
Patch available: MariaDB/server mariadb-10.6.28 (contains commit d5d741a3076f)
https://github.com/MariaDB/server/commit/d5d741a3076f911b468518d6b06a917593498c5bGitHub commit Patch Available
commit 9d4ffe23b258 (MariaDB/server)
Patch available: MariaDB/server mariadb-11.8.9 (contains commit 9d4ffe23b258)
https://github.com/MariaDB/server/commit/9d4ffe23b25808f7858b2dc48106fbd60cf0e513GitHub commit Patch Available
commit 5acb43522863 (MariaDB/server)
Patch available: MariaDB/server mariadb-10.6.28 (contains commit 5acb43522863)
https://github.com/MariaDB/server/commit/5acb43522863c9bd6b91f354104ea247bf513e9aGitHub commit Patch Available
commit 364656922575 (MariaDB/server)
Patch available: MariaDB/server mariadb-10.6.28 (contains commit 364656922575)
https://github.com/MariaDB/server/commit/3646569225758c8225e7342783d775ef7c7570e5GitHub commit Patch Available
commit 2b28d1c42410 (MariaDB/server)
Patch available: MariaDB/server mariadb-10.6.28 (contains commit 2b28d1c42410)
https://github.com/MariaDB/server/commit/2b28d1c424104429eeed43115ee6d8a803671d52Vendor Advisories for CVE-2026-86047(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | mariadb10-11-main-10.11.18-4.1.1.hum1 | 2026-10-19 | redhat |
| redhat | mariadb11-8-main-11.8.9-0.1.hum1 | 2026-10-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-20 15:47 UTCEG score recompute
- 2026-10-20 15:47 UTCVendor advisory
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-19 13:27 UTCEG score recompute
- 2026-10-19 13:27 UTCVendor advisory
- 2026-10-19 12:58 UTCEG score recompute
- 2026-10-19 12:58 UTCVendor advisory
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-18 03:05 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-16 17:55 UTCEG score recompute
- 2026-10-16 16:50 UTCEG score recomputeFirst assessed: 7.7 HIGH
- 2026-10-16 16:47 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
7 shownredhat:RHSA-2026:84689
Frequently asked(5)
What is CVE-2026-86047?
CVE-2026-86047 is a high-severity vulnerability; its CVE record was published on October 16, 2026. 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…
When was the CVE record for CVE-2026-86047 published?
The CVE record for CVE-2026-86047 was published on October 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-86047 actively exploited?
CVE-2026-86047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86047?
CVE-2026-86047 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86047?
A fix for CVE-2026-86047 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86047 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-86047
Is Your Infrastructure Affected by CVE-2026-86047?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.