← ← Back to all products
All badges & lifecycle API →
Apache NiFiEnd of Life (EOL) Dates & Support Status
Active
MiddlewareLatest Version: 2.12.0Latest Release: Sep 13, 2026
Apache NiFi is a dataflow management system for automating data movement between systems.
Support summary
Apache NiFi currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
23
Latest Version
2.12.0
Active Support
1
EOL
22
Lifecycle Timeline
Mar 11, 2025As of Sep 27, 2026
2.12Active · Date not announced
2.11EOL · Sep 13, 2026
2.10EOL · Aug 3, 2026
2.9EOL · Jun 18, 2026
2.8EOL · Apr 10, 2026
2.7EOL · Feb 13, 2026
2.6EOL · Dec 9, 2025
2.5EOL · Sep 21, 2025
2.4EOL · Jul 22, 2025
2.3EOL · May 1, 2025
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.12 | Sep 13, 2026 | Maintained | Date not announced | 2.12.0 | No | Active |
| 2.11 | Aug 3, 2026 | Ended | Sep 13, 2026 | 2.11.0 | No | EOL |
| 2.10 | Jun 18, 2026 | Ended | Aug 3, 2026 | 2.10.0 | No | EOL |
| 2.9 | Apr 10, 2026 | Ended | Jun 18, 2026 | 2.9.0 | No | EOL |
| 2.8 | Feb 13, 2026 | Ended | Apr 10, 2026 | 2.8.0 | No | EOL |
| 2.7 | Dec 9, 2025 | Ended | Feb 13, 2026 | 2.7.2 | No | EOL |
| 2.6 | Sep 21, 2025 | Ended | Dec 9, 2025 | 2.6.0 | No | EOL |
| 2.5 | Jul 22, 2025 | Ended | Sep 21, 2025 | 2.5.0 | No | EOL |
| 2.4 | May 1, 2025 | Ended | Jul 22, 2025 | 2.4.0 | No | EOL |
| 2.3 | Mar 11, 2025 | Ended | May 1, 2025 | 2.3.0 | No | EOL |
| 2.2 | Jan 27, 2025 | Ended | Mar 11, 2025 | 2.2.0 | No | EOL |
| 2.1 | Dec 23, 2024 | Ended | Jan 27, 2025 | 2.1.0 | No | EOL |
| 2.0 | Nov 1, 2024 | Ended | Dec 23, 2024 | 2.0.0 | No | EOL |
| 1.28 | Oct 26, 2024 | Ended | Dec 8, 2024 | 1.28.1 | No | EOL |
| 1.27 | Jul 7, 2024 | Ended | Oct 26, 2024 | 1.27.0 | No | EOL |
| 1.26 | May 6, 2024 | Ended | Jul 7, 2024 | 1.26.0 | No | EOL |
| 1.25 | Jan 29, 2024 | Ended | May 6, 2024 | 1.25.0 | No | EOL |
| 1.24 | Nov 27, 2023 | Ended | Jan 29, 2024 | 1.24.0 | No | EOL |
| 1.23 | Jul 25, 2023 | Ended | Nov 27, 2023 | 1.23.2 | No | EOL |
| 1.22 | Jun 11, 2023 | Ended | Jul 25, 2023 | 1.22.0 | No | EOL |
| 1.21 | Apr 7, 2023 | Ended | Jun 11, 2023 | 1.21.0 | No | EOL |
| 1.20 | Feb 9, 2023 | Ended | Apr 7, 2023 | 1.20.0 | No | EOL |
| 1.19 | Nov 28, 2022 | Ended | Feb 9, 2023 | 1.19.1 | No | EOL |
Data sources
Sources
Embed this badge
Show Apache NiFi's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/apache-nifi/)HTML
<a href="https://eol.wiki/apache-nifi/"><img src="https://eol.wiki/badge/apache-nifi.svg" alt="Apache NiFi end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Apache NiFi have reached end of life?
The following Apache NiFi versions have reached end of life and no longer receive security updates: 2.11, 2.10, 2.9, 2.8, 2.7, 2.6, 2.5, 2.4 (and 14 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Apache NiFi 2.11?
Apache NiFi 2.11 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache NiFi?
The latest version of Apache NiFi is 2.12.0, released in the 2.12 release cycle.
How many versions of Apache NiFi are currently supported?
Apache NiFi currently has 1 actively supported version(s): 2.12.
When does Apache NiFi 2.12 reach end of life?
Apache NiFi 2.12 does not have a specific end-of-life date announced yet.
What should I do when Apache NiFi reaches end of life?
When a Apache NiFi version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.