MariaDB Connector/J End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all MariaDB Connector/J versions. Dates read at the vendor's own lifecycle pages (mariadb.com). Updated at every deploy.
MariaDB Connector/J 4.0 is supported, with no end-of-life or end-of-support date announced yet. The next MariaDB Connector/J version to reach end of life is 3.5, in September 2031. 10 of 14 tracked MariaDB Connector/J versions are past end of life; the most recent to reach it, 2.7, did so in September 2026. The full MariaDB Connector/J lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.8 | 1.8.0 | Feb 8, 2019 | Jul 31, 2022 | 1552 days past EOL | EOL |
| 2.2 | 2.2.6 | Nov 8, 2017 | Sep 7, 2018 | 2975 days past EOL | EOL |
| 2.3 | 2.3.0 | Sep 6, 2018 | Jan 29, 2019 | 2831 days past EOL | EOL |
| 2.4 | 2.4.4 | Jan 29, 2019 | Nov 22, 2019 | 2534 days past EOL | EOL |
| 2.5 | 2.5.4 | Oct 3, 2019 | Mar 20, 2020 | 2415 days past EOL | EOL |
| 2.6 | 2.6.2 | Mar 19, 2020 | Sep 25, 2020 | 2226 days past EOL | EOL |
| 2.7 | 2.7.15 | Sep 24, 2020 | Sep 2026 | EOL since September 2026 | EOL |
| 3.0 | 3.0.11 | Jan 21, 2022 | Nov 2022 | EOL since November 2022 | EOL |
| 3.1 | 3.1.4 | Nov 10, 2022 | Not published | Past EOL | EOL |
| 3.2 | 3.2.0 | Aug 25, 2023 | Nov 2023 | EOL since November 2023 | EOL |
| 3.3 | 3.3.7 | Nov 7, 2023 | Sep 2031 | EOL in September 2031 | Active |
| 3.4 | 3.4.5 | May 17, 2024 | Sep 2031 | EOL in September 2031 | Active |
| 3.5 | 3.5.11 | Oct 24, 2024 | Sep 2031 | EOL in September 2031 | Active |
| 4.0 | 4.0.0 | Oct 21, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mariadb-connector-j)
MariaDB Connector/J lifecycle status — the real story
MariaDB Connector/J is MariaDB's own JDBC driver, published on Maven Central as org.mariadb.jdbc:mariadb-java-client. It is a client library that ships inside Java applications, so its lifecycle is separate from the MariaDB server's: a supported server can still be reached through a driver line that no longer gets fixes.
MariaDB's engineering policy gives each Connector/J line five years of standard support from general availability, then three years of extended support, with the end dates tied to Oracle's Java SE roadmap. The current policy table prints those dates to the month, so this page shows them as months, not days.
Older lines (the 2.x driver and the early 3.x releases) are often pinned in application dependency trees long after MariaDB stops fixing them. Dependency scanners find them by the Maven coordinate, and an unmaintained driver keeps any later security flaw unpatched unless the line is upgraded or covered by a third-party extended support build.
MariaDB Connector/J release and support pattern
Across the 14 release lines with a published release date, MariaDB Connector/J has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 10 months from its release to its end-of-life date (measured on the 12 lines with both dates published).
Of the 14 release lines tracked, 10 are past end of life and 4 are still within support; 1 is marked end of life without a published date. The newest line, 4.0, was released October 21, 2026. The next scheduled end of life is 3.5 in September 2031 (the vendor names the month only). The longest-supported line currently published is 3.3, to September 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does MariaDB Connector/J end of life mean for your organization?
When a version of MariaDB Connector/J reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL MariaDB Connector/J should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when MariaDB Connector/J reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your MariaDB Connector/J version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
MariaDB Connector/J has 10 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for MariaDB Connector/J exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans MariaDB Connector/J 3.1. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."