Apache ActiveMQ End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache ActiveMQ versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Apache ActiveMQ 6.3 is supported, with no end-of-life or end-of-support date announced yet. 21 of 24 tracked Apache ActiveMQ versions are past end of life; the most recent to reach it, 6.1, did so on December 2, 2025. The full Apache ActiveMQ 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 |
|---|---|---|---|---|---|
| 5.0 | 5.0.0 | Dec 7, 2007 | May 1, 2008 | 6719 days past EOL | EOL |
| 5.1 | 5.1.0 | May 1, 2008 | Jun 30, 2009 | 6294 days past EOL | EOL |
| 5.2 | 5.2.0 | Jun 30, 2009 | Oct 23, 2009 | 6179 days past EOL | EOL |
| 5.3 | 5.3.1 | Oct 23, 2009 | Aug 13, 2010 | 5885 days past EOL | EOL |
| 5.4 | 5.4.3 | Aug 13, 2010 | Oct 12, 2011 | 5460 days past EOL | EOL |
| 5.5 | 5.5.1 | Mar 28, 2011 | May 2, 2012 | 5257 days past EOL | EOL |
| 5.6 | 5.6.0 | May 2, 2012 | Oct 2, 2012 | 5104 days past EOL | EOL |
| 5.7 | 5.7.0 | Oct 2, 2012 | Feb 6, 2013 | 4977 days past EOL | EOL |
| 5.8 | 5.8.0 | Feb 6, 2013 | Oct 14, 2013 | 4727 days past EOL | EOL |
| 5.9 | 5.9.1 | Oct 14, 2013 | Jun 5, 2014 | 4493 days past EOL | EOL |
| 5.10 | 5.10.2 | Jun 5, 2014 | Feb 13, 2015 | 4240 days past EOL | EOL |
| 5.11 | 5.11.4 | Jan 30, 2015 | Feb 3, 2016 | 3885 days past EOL | EOL |
| 5.12 | 5.12.3 | Aug 10, 2015 | Feb 3, 2016 | 3885 days past EOL | EOL |
| 5.13 | 5.13.5 | Nov 30, 2015 | Dec 16, 2016 | 3568 days past EOL | EOL |
| 5.14 | 5.14.5 | Aug 2, 2016 | Jun 27, 2017 | 3375 days past EOL | EOL |
| 5.15 | 5.15.16 | Jun 27, 2017 | Mar 9, 2022 | 1659 days past EOL | EOL |
| 5.16 | 5.16.8 | Jun 25, 2020 | Mar 18, 2023 | 1285 days past EOL | EOL |
| 5.17 | 5.17.7 | Mar 9, 2022 | Apr 12, 2024 | 894 days past EOL | EOL |
| 5.18 | 5.18.7 | Mar 18, 2023 | Mar 11, 2025 | 561 days past EOL | EOL |
| 6.0 | 6.0.1 | Nov 14, 2023 | Mar 17, 2024 | 920 days past EOL | EOL |
| 6.1 | 6.1.8 | Mar 11, 2024 | Dec 2, 2025 | 295 days past EOL | EOL |
| 5.19 | 5.19.11 | Mar 7, 2025 | TBD | Supported | Active |
| 6.2 | 6.2.10 | Nov 9, 2025 | TBD | Supported | Active |
| 6.3 | 6.3.2 | Jul 24, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-activemq)
Apache ActiveMQ release and support pattern
Across the 24 release lines with a published release date, Apache ActiveMQ has shipped a new line roughly every 8 months (median interval). A line typically stays supported for about 11 months from its release to its end-of-life date (measured on the 21 lines with both dates published).
Of the 24 release lines tracked, 21 are past end of life and 3 are still within support. The newest line, 6.3, was released July 24, 2026. No end-of-life date is currently published for the 3 supported lines.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Apache ActiveMQ security intelligence
CISA KEV history: Apache ActiveMQ is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2026-04-16, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
Patch behavior after end of life: Mixed record. Apache backported the notorious CVE-2023-46604 fix to every EOL ActiveMQ line — then fixed KEV-listed CVE-2026-34197 only in the supported 5.19.4 and 6.2.3. The project's older generosity is not its current policy; treat modern EOL ActiveMQ lines as fix-less. (Observed behavior from our primary-source verification sweep, checked 2026-08-07 — never a guarantee of future fixes.)
What does Apache ActiveMQ end of life mean for your organization?
When a version of Apache ActiveMQ 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 Apache ActiveMQ 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 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, extended support vendors provide continued security patches for EOL Apache ActiveMQ versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Apache ActiveMQ has 21 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Apache ActiveMQ is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."