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

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
3.19 Sep 28, 2026—No—3.19.0—Active
3.18 Aug 20, 2026—Sep 28, 202625d ago3.18.0—EOL
3.17 Jun 16, 2026—Aug 20, 202664d ago3.17.0—EOL
3.16 Apr 8, 2026—Jun 16, 2026129d ago3.16.0—EOL
3.15 Feb 5, 2026—Apr 8, 2026198d ago3.15.0—EOL
3.14 Oct 10, 2025—Feb 5, 2026260d ago3.14.1—EOL
3.13 Jun 27, 2025—Oct 10, 2025378d ago3.13.0—EOL
3.12 Apr 1, 2025—Jun 27, 2025483d ago3.12.0—EOL
3.11 Oct 17, 2024—Apr 1, 2025570d ago3.11.0—EOL
3.10 Aug 14, 2024—Oct 17, 2024736d ago3.10.0—EOL
3.9 Mar 20, 2024—Aug 14, 2024800d ago3.9.1—EOL
3.8 Jan 9, 2024—Mar 20, 2024947d ago3.8.1—EOL
3.7 Nov 17, 2023—Jan 9, 20241018d ago3.7.0—EOL
3.6 Oct 1, 2023—Nov 17, 20231071d ago3.6.0—EOL
3.5 Aug 29, 2023—Oct 1, 20231118d ago3.5.0—EOL
3.4 Jun 27, 2023—Aug 29, 20231151d ago3.4.1—EOL
3.3 Apr 30, 2023—Jun 27, 20231214d ago3.3.0—EOL
3.2 LTSMar 6, 2023—Nov 13, 2024709d ago3.2.2—EOL
3.1 Dec 26, 2022—Mar 6, 20231327d ago3.1.0—EOL
3.0 Oct 26, 2022—Dec 26, 20221397d ago3.0.0—EOL
2.15 LTSJul 22, 2022—Mar 3, 20231330d ago2.15.3—EOL
2.14 May 23, 2022—Jul 22, 20221554d ago2.14.1—EOL
2.13 LTSMar 21, 2022—Aug 19, 20221526d ago2.13.3—EOL
2.12 Jan 20, 2022—Mar 21, 20221677d ago2.12.1—EOL
2.11 Nov 23, 2021—Jan 20, 20221737d ago2.11.0—EOL
2.10 LTSSep 24, 2021—Apr 1, 20221666d ago2.10.5—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions