Apache ActiveMQ Artemis End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache ActiveMQ Artemis versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | May 21, 2015 | Sep 15, 2015 | 3981 days past EOL | EOL |
| 1.1 | 1.1.0 | Sep 15, 2015 | Jan 4, 2016 | 3870 days past EOL | EOL |
| 1.2 | 1.2.0 | Jan 4, 2016 | Jun 9, 2016 | 3713 days past EOL | EOL |
| 1.3 | 1.3.0 | Jun 9, 2016 | Sep 6, 2016 | 3624 days past EOL | EOL |
| 1.4 | 1.4.0 | Sep 6, 2016 | Nov 3, 2016 | 3566 days past EOL | EOL |
| 1.5 | 1.5.6 | Nov 3, 2016 | Mar 12, 2018 | 3072 days past EOL | EOL |
| 2.0 | 2.0.0 | Mar 10, 2017 | May 8, 2017 | 3380 days past EOL | EOL |
| 2.1 | 2.1.0 | May 8, 2017 | Jul 25, 2017 | 3302 days past EOL | EOL |
| 2.2 | 2.2.0 | Jul 24, 2017 | Sep 5, 2017 | 3260 days past EOL | EOL |
| 2.3 | 2.3.0 | Sep 5, 2017 | Nov 1, 2017 | 3203 days past EOL | EOL |
| 2.4 | 2.4.0 | Nov 1, 2017 | Mar 12, 2018 | 3072 days past EOL | EOL |
| 2.5 | 2.5.0 | Mar 12, 2018 | May 16, 2018 | 3007 days past EOL | EOL |
| 2.6 | 2.6.4 | May 16, 2018 | Mar 14, 2019 | 2705 days past EOL | EOL |
| 2.7 | 2.7.0 | Mar 14, 2019 | May 2, 2019 | 2656 days past EOL | EOL |
| 2.8 | 2.8.1 | May 2, 2019 | May 30, 2019 | 2628 days past EOL | EOL |
| 2.9 | 2.9.0 | May 29, 2019 | Aug 26, 2019 | 2540 days past EOL | EOL |
| 2.10 | 2.10.1 | Aug 26, 2019 | Jan 10, 2020 | 2403 days past EOL | EOL |
| 2.11 | 2.11.0 | Jan 10, 2020 | Apr 21, 2020 | 2301 days past EOL | EOL |
| 2.12 | 2.12.0 | Apr 21, 2020 | May 16, 2020 | 2276 days past EOL | EOL |
| 2.13 | 2.13.0 | May 16, 2020 | Jul 9, 2020 | 2222 days past EOL | EOL |
| 2.14 | 2.14.0 | Jul 9, 2020 | Aug 24, 2020 | 2176 days past EOL | EOL |
| 2.15 | 2.15.0 | Aug 24, 2020 | Nov 2, 2020 | 2106 days past EOL | EOL |
| 2.16 | 2.16.0 | Nov 2, 2020 | Feb 11, 2021 | 2005 days past EOL | EOL |
| 2.17 | 2.17.0 | Feb 11, 2021 | Aug 9, 2021 | 1826 days past EOL | EOL |
| 2.18 | 2.18.0 | Aug 9, 2021 | Oct 11, 2021 | 1763 days past EOL | EOL |
| 2.19 | 2.19.1 | Oct 11, 2021 | Dec 15, 2021 | 1698 days past EOL | EOL |
| 2.20 | 2.20.0 | Dec 14, 2021 | Mar 22, 2022 | 1601 days past EOL | EOL |
| 2.21 | 2.21.0 | Mar 22, 2022 | Apr 27, 2022 | 1565 days past EOL | EOL |
| 2.22 | 2.22.0 | Apr 27, 2022 | Jun 7, 2022 | 1524 days past EOL | EOL |
| 2.23 | 2.23.1 | Jun 7, 2022 | Jul 26, 2022 | 1475 days past EOL | EOL |
| 2.24 | 2.24.0 | Jul 26, 2022 | Aug 30, 2022 | 1440 days past EOL | EOL |
| 2.25 | 2.25.0 | Aug 30, 2022 | Sep 21, 2022 | 1418 days past EOL | EOL |
| 2.26 | 2.26.0 | Sep 21, 2022 | Nov 8, 2022 | 1370 days past EOL | EOL |
| 2.27 | 2.27.1 | Nov 8, 2022 | Jan 31, 2023 | 1286 days past EOL | EOL |
| 2.28 | 2.28.0 | Jan 31, 2023 | Jun 14, 2023 | 1152 days past EOL | EOL |
| 2.29 | 2.29.0 | Jun 14, 2023 | Jul 20, 2023 | 1116 days past EOL | EOL |
| 2.30 | 2.30.0 | Jul 20, 2023 | Sep 15, 2023 | 1059 days past EOL | EOL |
| 2.31 | 2.31.2 | Sep 15, 2023 | Jan 24, 2024 | 928 days past EOL | EOL |
| 2.32 | 2.32.0 | Jan 24, 2024 | Mar 19, 2024 | 873 days past EOL | EOL |
| 2.33 | 2.33.0 | Mar 19, 2024 | May 29, 2024 | 802 days past EOL | EOL |
| 2.34 | 2.34.0 | May 29, 2024 | Jun 12, 2024 | 788 days past EOL | EOL |
| 2.35 | 2.35.0 | Jun 12, 2024 | Jul 25, 2024 | 745 days past EOL | EOL |
| 2.36 | 2.36.0 | Jul 25, 2024 | Aug 16, 2024 | 723 days past EOL | EOL |
| 2.37 | 2.37.0 | Aug 16, 2024 | Oct 16, 2024 | 662 days past EOL | EOL |
| 2.38 | 2.38.0 | Oct 16, 2024 | Dec 16, 2024 | 601 days past EOL | EOL |
| 2.39 | 2.39.0 | Dec 16, 2024 | Mar 13, 2025 | 514 days past EOL | EOL |
| 2.40 | 2.40.0 | Mar 13, 2025 | Apr 23, 2025 | 473 days past EOL | EOL |
| 2.41 | 2.41.0 | Apr 23, 2025 | Jul 14, 2025 | 391 days past EOL | EOL |
| 2.42 | 2.42.0 | Jul 14, 2025 | Oct 13, 2025 | 300 days past EOL | EOL |
| 2.43 | 2.43.0 | Oct 13, 2025 | Oct 29, 2025 | 284 days past EOL | EOL |
| 2.44 | 2.44.0 | Oct 29, 2025 | Jan 23, 2026 | 198 days past EOL | EOL |
| 2.50 | 2.50.0 | Jan 23, 2026 | Feb 11, 2026 | 179 days past EOL | EOL |
| 2.51 | 2.51.0 | Feb 11, 2026 | Mar 2, 2026 | 160 days past EOL | EOL |
| 2.52 | 2.52.0 | Mar 2, 2026 | Mar 17, 2026 | 145 days past EOL | EOL |
| 2.53 | 2.53.0 | Mar 17, 2026 | May 14, 2026 | 87 days past EOL | EOL |
| 2.54 | 2.54.0 | May 14, 2026 | Jun 23, 2026 | 47 days past EOL | EOL |
| 2.55 | 2.55.0 | Jun 23, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-artemis)
What does Apache ActiveMQ Artemis end of life mean for your organization?
When a version of Apache ActiveMQ Artemis 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Apache ActiveMQ Artemis 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 Apache ActiveMQ Artemis 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Apache ActiveMQ Artemis versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Apache ActiveMQ Artemis has 56 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Apache ActiveMQ Artemis exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.