CLN Login
MariaDB 10.6 reaches end of life on July 6. Keep your servers patched.
ELS for MariaDB delivers ongoing security patches for MariaDB 10.6 after the community cutoff. Updates arrive as drop-in replacements through the package manager you already use. No forced upgrade across your customers’ databases.
Community patches for MariaDB 10.6 stop on July 6, 2026. Every CVE after that is yours to deal with — unless you have ELS.
What changes on July 6, 2026
After July 6, MariaDB 10.6 keeps serving queries exactly as before. The problem is what builds up underneath it. New vulnerabilities that never get patched, auditors who start asking questions, and an ecosystem that quietly moves on.
Security
patches stop
The database holds the data and sits within reach of every app server. Once 10.6 stops getting fixes, attackers reverse-engineer each new patch in supported branches and hunt for the same flaw in the version that will never be patched.
Compliance
risk rises
PCI DSS, HIPAA, SOC 2, and FedRAMP all expect known vulnerabilities to be patched on a clock. An unsupported database can be the one finding that holds up an otherwise clean audit, and cyber-insurance reviews increasingly check for it.
One version,
every customer
On a hosting server, an EOL database doesn’t put one site at risk. It exposes every customer site that depends on it. The blast radius is your whole fleet.
A forced database upgrade is a churn risk, not a quick fix
Moving thousands of customer databases to a new major version means schema and config review, replication validation, application testing, and a downtime window. MariaDB 11.0 even changed the optimizer cost model, so some queries get slower. One compatibility break can take down customer sites that were running fine for years. Rushed migrations ship bugs, and bugs ship support tickets and cancellations.
The clean answer on a whiteboard is rarely the clean answer across a fleet.
Keep running MariaDB 10.6.
Stay secure.
Ongoing CVE
patches
Drop-in, through
your package
manager
The whole stack,
not just the
engine
Upgrade on your
own clock
How ELS for MariaDB works
Simple per-server pricing
Priced per server, with volume pricing that applies automatically as your server count grows.
Existing CloudLinux customers can enable ELS for MariaDB in the CloudLinux Network portal.
Frequently Asked Questions
Common questions from hosting providers evaluating Endless Lifecycle Support
No. ELS for MariaDB keeps you on the same 10.6 version and swaps the binaries for patched ones through your package manager. Your data, configuration, replication, and backup workflows stay exactly as they are.
In most cases, no. If your MariaDB 10.6 packages came from the CloudLinux or ELS repositories, enabling ELS and running a normal update is enough. If you installed MariaDB from a third-party repository, you repoint to the ELS repo and the package manager swaps the binaries. Your databases are not reinstalled.
Upgrading is the right long-term move, and ELS isn’t meant to replace it. ELS removes the deadline so you can plan and test that upgrade properly instead of rushing it before July 6. Many teams run both: ELS for coverage now, the major upgrade on a sane timeline.
MariaDB 10.6 on x86_64, across CloudLinux 7/8/9 and other EL 7/8/9 distributions today. Other MariaDB versions, architectures, and distributions are available on request.
Possibly, for CloudLinux 7 servers, if your MariaDB packages came from the CloudLinux ELS repo. We can help check your setup if you’re unsure.
For as long as you run MariaDB 10.6. ELS is designed to keep your deployment secure until you choose to move off it.