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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.0 | 5.0.0 | Dec 7, 2007 | May 1, 2008 | 6645 days past EOL | EOL |
| 5.1 | 5.1.0 | May 1, 2008 | Jun 30, 2009 | 6220 days past EOL | EOL |
| 5.2 | 5.2.0 | Jun 30, 2009 | Oct 23, 2009 | 6105 days past EOL | EOL |
| 5.3 | 5.3.1 | Oct 23, 2009 | Aug 13, 2010 | 5811 days past EOL | EOL |
| 5.4 | 5.4.3 | Aug 13, 2010 | Oct 12, 2011 | 5386 days past EOL | EOL |
| 5.5 | 5.5.1 | Mar 28, 2011 | May 2, 2012 | 5183 days past EOL | EOL |
| 5.6 | 5.6.0 | May 2, 2012 | Oct 2, 2012 | 5030 days past EOL | EOL |
| 5.7 | 5.7.0 | Oct 2, 2012 | Feb 6, 2013 | 4903 days past EOL | EOL |
| 5.8 | 5.8.0 | Feb 6, 2013 | Oct 14, 2013 | 4653 days past EOL | EOL |
| 5.9 | 5.9.1 | Oct 14, 2013 | Jun 5, 2014 | 4419 days past EOL | EOL |
| 5.10 | 5.10.2 | Jun 5, 2014 | Feb 13, 2015 | 4166 days past EOL | EOL |
| 5.11 | 5.11.4 | Jan 30, 2015 | Feb 3, 2016 | 3811 days past EOL | EOL |
| 5.12 | 5.12.3 | Aug 10, 2015 | Feb 3, 2016 | 3811 days past EOL | EOL |
| 5.13 | 5.13.5 | Nov 30, 2015 | Dec 16, 2016 | 3494 days past EOL | EOL |
| 5.14 | 5.14.5 | Aug 2, 2016 | Jun 27, 2017 | 3301 days past EOL | EOL |
| 5.15 | 5.15.16 | Jun 27, 2017 | Mar 9, 2022 | 1585 days past EOL | EOL |
| 5.16 | 5.16.8 | Jun 25, 2020 | Mar 18, 2023 | 1211 days past EOL | EOL |
| 5.17 | 5.17.7 | Mar 9, 2022 | Apr 12, 2024 | 820 days past EOL | EOL |
| 5.18 | 5.18.7 | Mar 18, 2023 | Mar 11, 2025 | 487 days past EOL | EOL |
| 6.0 | 6.0.1 | Nov 14, 2023 | Mar 17, 2024 | 846 days past EOL | EOL |
| 6.1 | 6.1.8 | Mar 11, 2024 | TBD | Supported | Active |
| 5.19 | 5.19.8 | Mar 7, 2025 | TBD | Supported | Active |
| 6.2 | 6.2.7 | Nov 9, 2025 | TBD | Supported | Active |
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: 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 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.
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 20 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →