MariaDB 10.6 reached end of life on July 6, 2026. 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.
What changed 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
The clean answer on a whiteboard is rarely the clean answer across a fleet.
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 might need tuning. 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.
Without ELS
Forced major upgrade
With ELS
Stay on 10.6, patched
Keep running MariaDB 10.6. Stay secure.
Keep your MariaDB 10.6 servers patched and supported — the engine and everything it depends on — so you can upgrade on your own schedule.
Ongoing CVE patches
ELS tracks new vulnerabilities in MariaDB 10.6 and backports the fixes to your open-source release, with SLA-backed delivery.
Drop-in, through your package manager
Patched builds of the same 10.6 version arrive as standard RPM updates through yum or dnf. No data migration, no schema changes, no app rewrites.
The whole stack, not just the engine
Coverage extends across MariaDB’s dependency graph: storage engines, system libraries, and crypto components, rebuilt and patched alongside the core.
Upgrade on your own clock
Security urgency stops driving your roadmap. Keep 10.6 patched now, and plan your move to a newer release when your team and customers are ready.
How ELS for MariaDB works
Track
ELS monitors CVEs across MariaDB 10.6 and its dependencies, drawing on vendor advisories, the NVD, and its own research.
Backport
Fixes are backported to your open-source 10.6 build, then tested for functionality and regressions.
Sign and publish
Patched packages are signed and published to the ELS repository for your distribution.
Update
Your package manager pulls the patched build like any other update. The engine stays 10.6; only the binaries get the fix.
Simple per-server pricing
Priced per server, with volume pricing that applies automatically as your server count grows.
Common questions from businesses 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.