MariaDB 10.9
MariaDB 10.9
The MariaDB 10.9 reached end of service life on Aug 22, 2023 — MariaDB no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your MariaDB 10.9 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- mariadb
- release
- 10.9
- product Label
- MariaDB
- release Label
- 10.9
- codename
- lts
- latest Version
- 10.9.8
- release Date
- 2022-08-15
- maintained
- source Url
- https://endoflife.date/mariadb
Lifecycle Dates
- End of Service Life
- Aug 22, 2023
- Last OEM Support
- Aug 22, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for MariaDB 10.9 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for MariaDB 10.9?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for MariaDB 10.9 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
MariaDB 10.9 Support: Frequently Asked Questions
Is the MariaDB 10.9 still supported?
MariaDB ended support for the MariaDB 10.9 on Aug 22, 2023 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the MariaDB 10.9 end of service life (EOSL) date?
MariaDB lists the end of service life for the MariaDB 10.9 as Aug 22, 2023.
Can I keep using the MariaDB 10.9 after its EOSL date?
Yes. EOSL means MariaDB stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the MariaDB 10.9 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting MariaDB 10.9
11 published CVEs affect the MariaDB 10.9, including 7 rated critical or high severity. MariaDB no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2022-32091 | HIGH | 7.5 | Jul 1, 2022 | MariaDB v10.7 was discovered to contain an use-after-poison in in __interceptor_memset at /libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc. |
| CVE-2022-32089 | HIGH | 7.5 | Jul 1, 2022 | MariaDB v10.5 to v10.7 was discovered to contain a segmentation fault via the component st_select_lex_unit::exclude_level. |
| CVE-2022-32084 | HIGH | 7.5 | Jul 1, 2022 | MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault via the component sub_select. |
| CVE-2022-32082 | HIGH | 7.5 | Jul 1, 2022 | MariaDB v10.5 to v10.7 was discovered to contain an assertion failure at table->get_ref_count() == 0 in dict0dict.cc. |
| CVE-2022-32081 | HIGH | 7.5 | Jul 1, 2022 | MariaDB v10.4 to v10.7 was discovered to contain an use-after-poison in prepare_inplace_add_virtual at /storage/innobase/handler/handler0alter.cc. |
| CVE-2022-27378 | HIGH | 7.5 | Apr 12, 2022 | An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements. |
| CVE-2018-25032 | HIGH | 7.5 | Mar 25, 2022 | zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches. |
| CVE-2026-35549 | MEDIUM | 6.5 | Apr 3, 2026 | An issue was discovered in MariaDB Server before 11.4.10, 11.5.x through 11.8.x before 11.8.6, and 12.x before 12.2.2. If the caching_sha2_password authentication plugin is installed, and some user accounts are configured to use it, a large packet can crash the server because sha256_crypt_r uses alloca. |
| CVE-2022-47015 | MEDIUM | 6.5 | Jan 20, 2023 | MariaDB Server before 10.3.34 thru 10.9.3 is vulnerable to Denial of Service. It is possible for function spider_db_mbase::print_warnings to dereference a null pointer. |
| CVE-2022-38791 | MEDIUM | 5.5 | Aug 27, 2022 | In MariaDB before 10.9.2, compress_write in extra/mariabackup/ds_compress.cc does not release data_mutex upon a stream write failure, which allows local users to trigger a deadlock. |
| CVE-2026-3494 | MEDIUM | 5.3 | Mar 3, 2026 | In MariaDB server version through 11.8.5, when server audit plugin is enabled with server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, if an authenticated database user invokes a SQL statement prefixed with double-hyphen (—) or hash (#) style comments, the statement is not logged. |