Apache Airflow End of Life Dates
other
Developers working with complex data engineering pipelines require a reliable workflow management platform to streamline their operations. Apache Airflow, created at Airbnb in October 2014, is an open-source solution that has been widely adopted to manage intricate workflows. The platform is maintained by the Apache Software Foundation, which ensures that it remains a viable option for developers due to its active community and continuous development. This workflow management platform has become essential for many developers, as it allows them to automate and monitor their workflows efficiently.
The end-of-life landscape for Apache Airflow currently consists of six versions, with five of them already reaching their end-of-life status. The latest stable version, 3.2.2, is the only active version at present. Recently, version 2 reached its end-of-life on 2026-04-22, marking a significant milestone in the platform's lifecycle. Since there is no announced next end-of-life date, developers can continue to use the latest stable version without immediate concern for its expiration. This provides a stable foundation for developers to build and manage their data engineering pipelines.
Given the current security landscape, Apache Airflow has a clean slate with zero tracked CVEs and no critical vulnerabilities. As a result, there is no most affected version, and no known vulnerabilities pose an immediate threat to users. With its strong security posture, developers can confidently rely on Apache Airflow for their workflow management needs. To maintain the security and integrity of their pipelines, developers should continue to monitor the platform's development and update to the latest stable version as necessary, ensuring they remain up-to-date with the latest features and security patches.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.3 | Jul 6, 2026 | — | No | — | 3.3.0 | — | Active | |
| 3.2 | Apr 7, 2026 | Jul 6, 2026 | Jul 6, 2026 | 18d ago | 3.2.2 | — | EOL | |
| 3.1 | Sep 25, 2025 | Apr 7, 2026 | Apr 7, 2026 | 108d ago | 3.1.8 | — | EOL | |
| 3.0 | Apr 22, 2025 | Sep 25, 2025 | Sep 25, 2025 | 302d ago | 3.0.6 | — | EOL | |
| 3 | Apr 22, 2025 | — | No | — | 3.3.0 | — | Active | |
| 2 | Dec 17, 2020 | Oct 22, 2025 | Apr 22, 2026 | 93d ago | 2.11.2 | — | EOL | |
| 1.10 | Aug 27, 2018 | Dec 17, 2020 | Jun 17, 2021 | 1863d ago | 1.10.15 | — | EOL | |
| 1.9 | Jan 2, 2018 | Aug 27, 2018 | Aug 27, 2018 | 2888d ago | 1.9.0 | — | EOL | |
| 1.8 | May 9, 2017 | Jan 3, 2018 | Jan 3, 2018 | 3124d ago | 1.8.2 | — | EOL | |
| 1.7 | Mar 28, 2016 | Mar 19, 2017 | Mar 19, 2017 | 3414d ago | 1.7.1.2 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
