MariaDB: Seven Vulnerabilities Including Three Critical Flaws Disclosed Together
MariaDB addresses seven vulnerabilities, including three critical flaws, disclosed on October 16, 2026, impacting multiple server versions.

Key findings
- Seven vulnerabilities in MariaDB server disclosed on October 16, 2026, including three critical and three high-severity flaws.
- Critical flaws include bypass of table-name encoding (CVE-2026-92262) and use-after-free in SYS_REFCURSOR handling (CVE-2026-85748).
- High-severity issues involve incorrect privilege checks with GRANT PROXY (CVE-2026-97380) and identifier quoting problems (CVE-2026-86047).
- Vulnerabilities affect a wide range of MariaDB versions from 10.6.1 up to recent patch releases.
- Users are urged to update to patched versions to mitigate risks of data manipulation and unauthorized access.
On October 16, 2026, MariaDB released security updates addressing a batch of seven vulnerabilities, including three critical and three high-severity flaws. These vulnerabilities, disclosed simultaneously, impact various versions of the MariaDB server, a popular community-developed fork of MySQL. The disclosures highlight potential risks ranging from privilege escalation to buffer overflows, underscoring the importance of timely patching for database systems.
Several critical vulnerabilities were detailed in the advisory. CVE-2026-92262, with a CVSSv3 score of 9.9, allows attackers to bypass normal table-name filesystem encoding using a specific prefix, potentially leading to unauthorized access or manipulation of data. Another critical flaw, CVE-2026-85748 (CVSSv3 9.9), affects SYS_REFCURSOR handling and can lead to a use-after-free condition, exploitable by low-privileged attackers who open a large number of cursors. Additionally, CVE-2026-85746, also rated critical (CVSSv3 9.9), involves a buffer overflow in the ST_AsText function when converting nested GeometryCollections, which could be triggered by malformed geometry data.
High-severity issues were also prominent in this disclosure. CVE-2026-97380 (CVSSv3 8.8) stems from an issue with the GRANT PROXY statement, where an empty password in the IDENTIFIED clause is mishandled, leading to incorrect grantor privilege checks. CVE-2026-86047 (CVSSv3 7.7) impacts commands like SHOW CREATE SERVER and SHOW CREATE USER, as well as mariadb-dump, due to inconsistent identifier quoting, potentially allowing low-privileged attackers to inject or manipulate data.
The batch also included medium-severity vulnerabilities. CVE-2026-85985 (CVSSv3 5.4) concerns the CONNECT engine plugin's file-access User-Defined Functions (UDFs), which do not properly enforce FILE privileges or secure file operations, potentially allowing unauthorized file access. CVE-2026-85745 (CVSSv3 4.3) is a medium-severity flaw where ST_Area reads beyond an allocated buffer when processing invalid WKB for a MultiPolygon, due to a parser that advances without proper validation.
The affected versions for most of these vulnerabilities span from 10.6.1 up to specific patch releases in the 10.6, 10.11, 11.4, 11.8, 12.3, and 13.0 release lines. For instance, CVE-2026-97380, CVE-2026-92262, CVE-2026-86047, CVE-2026-85985, and CVE-2026-85746 affect versions up to 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2. CVE-2026-85748 specifically impacts versions 12.3.1 through 12.3.3 and 13.0.2. MariaDB has released updates to address these issues, and users are strongly advised to update to the patched versions to mitigate these risks.
This coordinated disclosure of multiple vulnerabilities, including critical and high-severity flaws, highlights the ongoing security challenges in database management systems. Users of MariaDB are urged to review the specific versioning details for each CVE and apply the necessary patches promptly to protect their environments from potential exploitation. Staying informed about these security updates is crucial for maintaining the integrity and security of sensitive data.