MariaDB Community Server 16 November 2026 releases fix thirteen CVEs
Identifiers: CVE-2026-101802 · CVE-2026-101796 · CVE-2026-101794 · CVE-2026-101775 · CVE-2026-101747 · CVE-2026-101725 · CVE-2026-101679 · CVE-2026-101619 · CVE-2026-101618 · CVE-2026-101617 · CVE-2026-101615 · CVE-2026-101614 · CVE-2026-101608
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
On 16 November 2026 MariaDB published Community Server 12.3.4, 11.8.10, 11.4.14 and 10.11.20. The release notes list fixes for thirteen CVEs: CVE-2026-101802, CVE-2026-101796, CVE-2026-101794, CVE-2026-101775, CVE-2026-101747, CVE-2026-101725, CVE-2026-101679, CVE-2026-101619, CVE-2026-101618, CVE-2026-101617, CVE-2026-101615, CVE-2026-101614 and CVE-2026-101608. The vendor catalog shows a CVE publication date of 20 October 2026 for all of them, which is a record date rather than a sign of brand-new discoveries.
Impact
CVSS v3.1 base scores range from 4.4 to 7.5. Two entries sit at 7.5 and one at 7.4, with most of the remainder at 6.5 or 4.9. The vendor catalog does not describe which server components are involved, what access a caller would need, or whether the issues affect availability or data. Because those prerequisites are not qualified, the actual scope and urgency for a given server have to be assessed by whoever administers it, taking into account how the database is exposed and who can connect to it. This briefing does not imply that any deployment is clear of risk.
Who is affected
This concerns self-hosted MariaDB Community Server on the 12.3, 11.8, 11.4 and 10.11 branches. The catalog only states the fixed versions, so we cannot say every earlier build is affected. Oracle MySQL, MariaDB Enterprise Server and client libraries are separate products with their own advisories. Linux distribution packages often carry backported fixes under different version numbers, so check your distribution's security notes before judging a server out of date.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| MariaDB Community Server | Exact introduced/affected ranges vary by CVE and are not established by the vendor fixed-version catalog | 12.3.4; 11.8.10; 11.4.14; 10.11.20 |
Exploitation evidence
Exploitation not established. No exploitation activity was described in the reviewed vendor catalog or release notes. The absence of such a statement is not evidence that exploitation has not occurred.
Actions
- Ask whoever runs your database for the exact MariaDB version and branch in use, including any managed or hosted instance, and have them assess exposure and who can connect.
- Apply the vendor-supported update within the same major branch: 12.3.4, 11.8.10, 11.4.14 or 10.11.20. Do not jump major versions just for this fix.
- If your operating system supplies MariaDB, prefer the distribution's patched package or backport and confirm it references these CVEs.
- Take a verified backup and test restore before updating, and schedule the restart during a compatible maintenance window.
- After the restart, confirm the running version and check that the site connects and reads and writes normally.
Unknowns
- Exact introduced and affected version ranges for each CVE are not given in the vendor catalog.
- Component, privilege and network prerequisites for each CVE were not described in the reviewed sources, so urgency for a specific server cannot be rated here.
- Whether the 10.6 branch receives any corresponding fix is not shown in the reviewed catalog rows.
Sources
Change history
- — Published: Published 17 November 2026 after reviewing the MariaDB CVE catalog and 11.4.14 release notes for the 16 November 2026 releases.