Apache Nifi End of Life Dates
other
Developers working with data integration and automation rely on a robust tool to manage the flow of data between software systems, which is where Apache NiFi comes into play. Created by the Apache Software Foundation, this software project is designed to automate and manage the flow of data, leveraging the concept of extract, transform, load, commonly referred to as ETL. The foundation maintains Apache NiFi, ensuring it continues to meet the evolving needs of developers. Since its inception, Apache NiFi has been a go-to solution for developers due to its flexibility and scalability in managing complex data flows.
The end-of-life landscape for Apache NiFi is relatively straightforward, with a total of 20 versions released to date. Out of these, 19 versions have reached their end-of-life, leaving only one active version. The latest stable version, 2.9.0, is the current benchmark for developers. Notably, the last end-of-life date was recorded on 2026-04-10 for version 2.8, but there is no next scheduled end-of-life date announced. This provides developers with a stable environment to work with, knowing that their current version will not be deprecated in the near future.
From a security standpoint, Apache NiFi presents a clean slate, with no recorded Common Vulnerabilities and Exposures, or CVEs, and consequently, no critical CVEs. This implies that the most affected version is nonexistent, given the absence of any vulnerabilities. Furthermore, there is no Known Exploited Vulnerability, or KEV, status to consider. Given this security picture, developers can confidently continue to use Apache NiFi for their data integration needs without immediate concerns about patching or upgrading due to security vulnerabilities. However, it is always prudent for developers to stay updated with the latest versions and security advisories to ensure the long-term integrity of their data flows.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2.10 | Jun 18, 2026 | — | No | — | 2.10.0 | — | Active | |
| 2.9 | Apr 10, 2026 | — | Jun 18, 2026 | 36d ago | 2.9.0 | — | EOL | |
| 2.8 | Feb 13, 2026 | — | Apr 10, 2026 | 105d ago | 2.8.0 | — | EOL | |
| 2.7 | Dec 9, 2025 | — | Feb 13, 2026 | 161d ago | 2.7.2 | — | EOL | |
| 2.6 | Sep 21, 2025 | — | Dec 9, 2025 | 227d ago | 2.6.0 | — | EOL | |
| 2.5 | Jul 22, 2025 | — | Sep 21, 2025 | 306d ago | 2.5.0 | — | EOL | |
| 2.4 | May 1, 2025 | — | Jul 22, 2025 | 367d ago | 2.4.0 | — | EOL | |
| 2.3 | Mar 11, 2025 | — | May 1, 2025 | 449d ago | 2.3.0 | — | EOL | |
| 2.2 | Jan 27, 2025 | — | Mar 11, 2025 | 500d ago | 2.2.0 | — | EOL | |
| 2.1 | Dec 23, 2024 | — | Jan 27, 2025 | 543d ago | 2.1.0 | — | EOL | |
| 2.0 | Nov 1, 2024 | — | Dec 23, 2024 | 578d ago | 2.0.0 | — | EOL | |
| 1.28 | Oct 26, 2024 | — | Dec 8, 2024 | 593d ago | 1.28.1 | — | EOL | |
| 1.27 | Jul 7, 2024 | — | Oct 26, 2024 | 636d ago | 1.27.0 | — | EOL | |
| 1.26 | May 6, 2024 | — | Jul 7, 2024 | 747d ago | 1.26.0 | — | EOL | |
| 1.25 | Jan 29, 2024 | — | May 6, 2024 | 809d ago | 1.25.0 | — | EOL | |
| 1.24 | Nov 27, 2023 | — | Jan 29, 2024 | 907d ago | 1.24.0 | — | EOL | |
| 1.23 | Jul 25, 2023 | — | Nov 27, 2023 | 970d ago | 1.23.2 | — | EOL | |
| 1.22 | Jun 11, 2023 | — | Jul 25, 2023 | 1095d ago | 1.22.0 | — | EOL | |
| 1.21 | Apr 7, 2023 | — | Jun 11, 2023 | 1139d ago | 1.21.0 | — | EOL | |
| 1.20 | Feb 9, 2023 | — | Apr 7, 2023 | 1204d ago | 1.20.0 | — | EOL | |
| 1.19 | Nov 28, 2022 | — | Feb 9, 2023 | 1261d ago | 1.19.1 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
