CVE-2026-107823

MariaDB: privilege escalation via incorrect view frm parsing

  • High 7.2

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, the MariaDB view FRM parser did not safely encode embedded newline characters in a username. An account with CREATE USER and CREATE VIEW WITH GRANT OPTION could create a crafted username containing additional view metadata, causing the parser to interpret part of the username as security metadata and potentially escalating database privileges. 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.

Key facts

Published
9 Oct 2026
Last changed
13 Oct 2026
Assigned by
GitHub_M
EPSS
0.786% likely to be exploited in the next 30 days, higher than 56.742% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.2CVSS 3.1, Highfrom the CNA (GitHub_M)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
MariaDBserver
  • >= 10.6.1, < 10.6.28 (affected)
  • >= 10.11.1, < 10.11.19 (affected)
  • >= 11.4.1, < 11.4.13 (affected)
  • >= 11.8.1, < 11.8.9 (affected)
  • >= 12.3.1, < 12.3.3 (affected)
  • >= 13.0.1, < 13.0.2 (affected)

Timeline

  1. 9 Oct 2026 Published

Weakness

References