MariaDB 11.1
MariaDB 11.1
The MariaDB 11.1 reached end of service life on Aug 21, 2024 — 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 11.1 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
- 11.1
- product Label
- MariaDB
- release Label
- 11.1
- codename
- lts
- latest Version
- 11.1.6
- release Date
- 2023-08-21
- maintained
- source Url
- https://endoflife.date/mariadb
Lifecycle Dates
- End of Service Life
- Aug 21, 2024
- Last OEM Support
- Aug 21, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for MariaDB 11.1 — 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 11.1?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for MariaDB 11.1 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 11.1 Support: Frequently Asked Questions
Is the MariaDB 11.1 still supported?
MariaDB ended support for the MariaDB 11.1 on Aug 21, 2024 — 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 11.1 end of service life (EOSL) date?
MariaDB lists the end of service life for the MariaDB 11.1 as Aug 21, 2024.
Can I keep using the MariaDB 11.1 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 11.1 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 11.1
4 published CVEs affect the MariaDB 11.1. MariaDB no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| 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-2024-27766 | MEDIUM | 5.7 | Oct 17, 2024 | An issue in MariaDB v.11.1 allows a remote attacker to execute arbitrary code via the lib_mysqludf_sys.so function. NOTE: this is disputed by the MariaDB Foundation because no privilege boundary is crossed. |
| 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. |
| CVE-2023-22084 | MEDIUM | 4.9 | Oct 17, 2023 | Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.43 and prior, 8.0.34 and prior and 8.1.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability im |