Apache Apisix End of Life Dates
other
Developers rely on Apache Apisix, a popular open-source project, to manage their API gateways efficiently. Created to provide a robust and scalable solution, Apache Apisix has been maintained by the Apache Software Foundation since its inception. The foundation's dedication to the project ensures that developers have access to a reliable and constantly evolving tool. With a wide range of features and a strong community backing, Apache Apisix has become a go-to choice for many developers seeking to streamline their API management processes.
The end-of-life landscape for Apache Apisix is characterized by a large number of versions that have already reached the end of their support cycle. Out of the 23 total versions, 22 have been marked as end-of-life, leaving only one active version currently supported. The latest stable version, 3.16.0, is the recommended choice for developers looking to ensure they have the latest security patches and features. Notably, the last end-of-life date was April 8, 2026, for version 3.15, and with no next EOL date announced, developers can focus on planning their upgrades without immediate pressure.
From a security perspective, Apache Apisix boasts an impressive track record, with zero total CVEs tracked and zero critical CVEs reported. As a result, there is no most affected version, and the project does not have a Known Exploited Vulnerability status. This pristine security record is a testament to the dedication of the Apache Software Foundation and the developer community. Given this information, developers can continue to use Apache Apisix with confidence, focusing on leveraging its features to improve their API management capabilities without worrying about imminent security risks or required upgrades to address known vulnerabilities.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.19 | Sep 28, 2026 | — | No | — | 3.19.0 | — | Active | |
| 3.18 | Aug 20, 2026 | — | Sep 28, 2026 | 25d ago | 3.18.0 | — | EOL | |
| 3.17 | Jun 16, 2026 | — | Aug 20, 2026 | 64d ago | 3.17.0 | — | EOL | |
| 3.16 | Apr 8, 2026 | — | Jun 16, 2026 | 129d ago | 3.16.0 | — | EOL | |
| 3.15 | Feb 5, 2026 | — | Apr 8, 2026 | 198d ago | 3.15.0 | — | EOL | |
| 3.14 | Oct 10, 2025 | — | Feb 5, 2026 | 260d ago | 3.14.1 | — | EOL | |
| 3.13 | Jun 27, 2025 | — | Oct 10, 2025 | 378d ago | 3.13.0 | — | EOL | |
| 3.12 | Apr 1, 2025 | — | Jun 27, 2025 | 483d ago | 3.12.0 | — | EOL | |
| 3.11 | Oct 17, 2024 | — | Apr 1, 2025 | 570d ago | 3.11.0 | — | EOL | |
| 3.10 | Aug 14, 2024 | — | Oct 17, 2024 | 736d ago | 3.10.0 | — | EOL | |
| 3.9 | Mar 20, 2024 | — | Aug 14, 2024 | 800d ago | 3.9.1 | — | EOL | |
| 3.8 | Jan 9, 2024 | — | Mar 20, 2024 | 947d ago | 3.8.1 | — | EOL | |
| 3.7 | Nov 17, 2023 | — | Jan 9, 2024 | 1018d ago | 3.7.0 | — | EOL | |
| 3.6 | Oct 1, 2023 | — | Nov 17, 2023 | 1071d ago | 3.6.0 | — | EOL | |
| 3.5 | Aug 29, 2023 | — | Oct 1, 2023 | 1118d ago | 3.5.0 | — | EOL | |
| 3.4 | Jun 27, 2023 | — | Aug 29, 2023 | 1151d ago | 3.4.1 | — | EOL | |
| 3.3 | Apr 30, 2023 | — | Jun 27, 2023 | 1214d ago | 3.3.0 | — | EOL | |
| 3.2 LTS | Mar 6, 2023 | — | Nov 13, 2024 | 709d ago | 3.2.2 | — | EOL | |
| 3.1 | Dec 26, 2022 | — | Mar 6, 2023 | 1327d ago | 3.1.0 | — | EOL | |
| 3.0 | Oct 26, 2022 | — | Dec 26, 2022 | 1397d ago | 3.0.0 | — | EOL | |
| 2.15 LTS | Jul 22, 2022 | — | Mar 3, 2023 | 1330d ago | 2.15.3 | — | EOL | |
| 2.14 | May 23, 2022 | — | Jul 22, 2022 | 1554d ago | 2.14.1 | — | EOL | |
| 2.13 LTS | Mar 21, 2022 | — | Aug 19, 2022 | 1526d ago | 2.13.3 | — | EOL | |
| 2.12 | Jan 20, 2022 | — | Mar 21, 2022 | 1677d ago | 2.12.1 | — | EOL | |
| 2.11 | Nov 23, 2021 | — | Jan 20, 2022 | 1737d ago | 2.11.0 | — | EOL | |
| 2.10 LTS | Sep 24, 2021 | — | Apr 1, 2022 | 1666d ago | 2.10.5 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
