cve.bz

CVE-2026-86047 mariadb mariadb: SQL Injection

7.7 highEPSS 0.9%Fix available

High (7.7) in mariadb mariadb. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-86047 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86047?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86047?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86047 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
mariadb:mariadbfrom 10.6.1 before 10.6.28
mariadb:mariadbfrom 10.11.1 before 10.11.19
mariadb:mariadbfrom 11.4.1 before 11.4.13
mariadb:mariadbfrom 11.8.1 before 11.8.9
mariadb:mariadbfrom 12.3.1 before 12.3.3
mariadb:mariadb13.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12mariadb10.11.19-0+deb12u1DEBIAN-CVE-2026-86047
Debian13mariadbno fix listedDEBIAN-CVE-2026-86047
Debian14mariadb1:11.8.9+ds-1DEBIAN-CVE-2026-86047
Ubuntu16.04:LTSmariadb-10.0no fix listedUBUNTU-CVE-2026-86047
Ubuntu18.04:LTSmariadb-10.1no fix listedUBUNTU-CVE-2026-86047
Ubuntu20.04:LTSmariadb-10.3no fix listedUBUNTU-CVE-2026-86047
Ubuntu22.04:LTSmariadb-10.6no fix listedUBUNTU-CVE-2026-86047
Ubuntu24.04:LTS, 26.04:LTS, 26.10mariadbno fix listedUBUNTU-CVE-2026-86047
Red Hathummingbird:1mariadb10.11, mariadb10.11-pam, mariadb10.11-test and 17 more0:10.11.18-4.1.1.hum1RHSA-2026:84701
Red Hathummingbird:1mariadb11.8, mariadb11.8-pam, mariadb11.8-test and 18 more3:11.8.9-0.1.hum1RHSA-2026:84689
openSUSETumbleweedmariadb12.3.2-3.1openSUSE-SU-2026:12245-1
Alpaquita23mariadb10.6.28-r0BELL-CVE-2026-86047
Alpaquita25mariadb11.4.13-r0BELL-CVE-2026-86047
Alpaquitastreammariadb11.8.9-r0BELL-CVE-2026-86047

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity for Red Hat Enterprise Linux environments because an attacker with minimal database privileges can compromise the integrity of administrative operations, potentially resulting in elevated SQL execution. In typical enterprise deployments where MariaDB hosts multi-tenant databases or permits unprivileged users to define schema objects, serialization routines fail to properly sanitize object identifiers. Consequently, when automated backup workflows or system administrators process and reapply generated schema exports or user definitions, injected commands execute under the context of the importing administrative account.

Red Hat's mitigation

Upgrade to the fixed version of MariaDB Server

ProductPackageStateAdvisory
Red Hat Hardened Imagesmariadb11-8-main-11.8.9-0.1.hum1Fixed 2026-10-19RHSA-2026:84689
Red Hat Hardened Imagesmariadb10-11-main-10.11.18-4.1.1.hum1Fixed 2026-10-19RHSA-2026:84701
Red Hat Enterprise Linux 10mariadb10.11Affected
Red Hat Enterprise Linux 10mariadb11.8Affected
Red Hat Enterprise Linux 7mariadbAffected
Red Hat Enterprise Linux 8mariadb:10.11/mariadbAffected
Red Hat Enterprise Linux 8mariadb:10.3/mariadbAffected
Red Hat Enterprise Linux 8mariadb-devel:10.3/mariadbAffected
Red Hat Enterprise Linux 9mariadbAffected
Red Hat Enterprise Linux 9mariadb:10.11/mariadbAffected
Red Hat Enterprise Linux 9mariadb:11.8/mariadbAffected
Red Hat OpenStack Platform 13 (Queens)mariadbAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-86047.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON