Apache Activemq End of Life Dates
other
Developers rely on Apache Activemq, a messaging and integration pattern server, to facilitate communication between systems. Created to address the need for a robust and scalable messaging platform, Apache Activemq has been maintained by the Apache Software Foundation since its inception. The foundation's ongoing support and development have made Apache Activemq a go-to solution for developers seeking a reliable and efficient messaging system. With its ability to support a wide range of protocols and integrate with various systems, Apache Activemq has become a crucial component in many software architectures.
The end-of-life landscape for Apache Activemq is characterized by a large number of versions that have reached the end of their support cycle. Out of the 23 versions that have been released, 20 are no longer supported, leaving only 3 active versions. The latest stable version, 6.2.6, is currently the recommended version for use. Although there is no next scheduled end-of-life date, the last version to reach end-of-life was 5.18, which occurred on 2025-03-11. This highlights the importance of staying up-to-date with the latest versions and planning upgrades accordingly to ensure continued support and security.
The security picture for Apache Activemq is currently favorable, with no known Common Vulnerabilities and Exposures (CVEs) tracked. This means that there are no critical or non-critical vulnerabilities that have been identified in any version of Apache Activemq. As a result, developers do not need to take immediate action to address any security concerns. However, it is still essential to continue monitoring the security landscape and planning for future upgrades to ensure the continued security and stability of their systems. By staying informed about the latest developments and updates, developers can ensure that their use of Apache Activemq remains secure and reliable.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 6.3 | Jul 24, 2026 | — | No | — | 6.3.2 | — | Active | |
| 6.2 | Nov 9, 2025 | — | No | — | 6.2.9 | — | Active | |
| 5.19 | Mar 7, 2025 | — | No | — | 5.19.11 | — | Active | |
| 6.1 | Mar 11, 2024 | — | Dec 2, 2025 | 279d ago | 6.1.8 | — | EOL | |
| 6.0 | Nov 14, 2023 | — | Mar 17, 2024 | 904d ago | 6.0.1 | — | EOL | |
| 5.18 | Mar 18, 2023 | — | Mar 11, 2025 | 545d ago | 5.18.7 | — | EOL | |
| 5.17 | Mar 9, 2022 | — | Apr 12, 2024 | 878d ago | 5.17.7 | — | EOL | |
| 5.16 | Jun 25, 2020 | — | Mar 18, 2023 | 1269d ago | 5.16.8 | — | EOL | |
| 5.15 | Jun 27, 2017 | — | Mar 9, 2022 | 1643d ago | 5.15.16 | — | EOL | |
| 5.14 | Aug 2, 2016 | — | Jun 27, 2017 | 3359d ago | 5.14.5 | — | EOL | |
| 5.13 | Nov 30, 2015 | — | Dec 16, 2016 | 3552d ago | 5.13.5 | — | EOL | |
| 5.12 | Aug 10, 2015 | — | Feb 3, 2016 | 3869d ago | 5.12.3 | — | EOL | |
| 5.11 | Jan 30, 2015 | — | Feb 3, 2016 | 3869d ago | 5.11.4 | — | EOL | |
| 5.10 | Jun 5, 2014 | — | Feb 13, 2015 | 4224d ago | 5.10.2 | — | EOL | |
| 5.9 | Oct 14, 2013 | — | Jun 5, 2014 | 4477d ago | 5.9.1 | — | EOL | |
| 5.8 | Feb 6, 2013 | — | Oct 14, 2013 | 4711d ago | 5.8.0 | — | EOL | |
| 5.7 | Oct 2, 2012 | — | Feb 6, 2013 | 4961d ago | 5.7.0 | — | EOL | |
| 5.6 | May 2, 2012 | — | Oct 2, 2012 | 5088d ago | 5.6.0 | — | EOL | |
| 5.5 | Mar 28, 2011 | — | May 2, 2012 | 5241d ago | 5.5.1 | — | EOL | |
| 5.4 | Aug 13, 2010 | — | Oct 12, 2011 | 5444d ago | 5.4.3 | — | EOL | |
| 5.3 | Oct 23, 2009 | — | Aug 13, 2010 | 5869d ago | 5.3.1 | — | EOL | |
| 5.2 | Jun 30, 2009 | — | Oct 23, 2009 | 6163d ago | 5.2.0 | — | EOL | |
| 5.1 | May 1, 2008 | — | Jun 30, 2009 | 6278d ago | 5.1.0 | — | EOL | |
| 5.0 | Dec 7, 2007 | — | May 1, 2008 | 6703d ago | 5.0.0 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
