Flux End of Life Dates
other
Developers rely on Flux to stay informed about the lifecycle of their preferred tools and technologies, and for good reason. Created to provide transparency into the often complex world of software support and maintenance, Flux has been a trusted resource for many years. The Flux project is maintained by a team dedicated to ensuring that users have access to the most current and accurate information available. By providing a centralized location for tracking end-of-life dates, supported versions, and security patch timelines, Flux helps developers plan their upgrades and migrations with confidence.
The landscape of Flux versions is characterized by a total of 10 distinct releases, with 7 of these having already reached their end-of-life. Currently, 3 versions remain actively supported, with the latest stable version being 2.6.4. Notably, the most recent end-of-life date was February 24, 2026, which marked the end of support for version 2.5. While there is no next scheduled end-of-life date announced, developers should remain vigilant and continue to monitor the status of their deployed versions to ensure they are adequately prepared for any future changes.
From a security perspective, Flux has a remarkably clean record, with a total of 0 tracked CVEs and no critical vulnerabilities reported. As a result, there is no most affected version to highlight, and no urgent action is required from developers in response to known security threats. Nevertheless, it is essential for users to remain proactive and keep their Flux installations up to date, as this will help mitigate any potential risks that may arise in the future. By doing so, developers can ensure the continued stability and security of their systems, even in the absence of known vulnerabilities.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2.9 | Jun 30, 2026 | — | No | — | 2.9.5 | — | Active | |
| 2.8 | Feb 24, 2026 | — | No | — | 2.8.8 | — | Active | |
| 2.7 | Sep 30, 2025 | — | No | — | 2.7.5 | — | Active | |
| 2.6 | May 29, 2025 | — | Jun 30, 2026 | 69d ago | 2.6.4 | — | EOL | |
| 2.5 | Feb 20, 2025 | — | Feb 24, 2026 | 195d ago | 2.5.1 | — | EOL | |
| 2.4 | Sep 30, 2024 | — | Sep 30, 2025 | 342d ago | 2.4.0 | — | EOL | |
| 2.3 | May 13, 2024 | — | May 29, 2025 | 466d ago | 2.3.0 | — | EOL | |
| 2.2 | Dec 12, 2023 | — | Feb 20, 2025 | 564d ago | 2.2.3 | — | EOL | |
| 2.1 | Aug 24, 2023 | — | Sep 30, 2024 | 707d ago | 2.1.2 | — | EOL | |
| 2.0 | Jul 5, 2023 | — | May 13, 2024 | 847d ago | 2.0.1 | — | EOL | |
| 1.25 | Mar 30, 2022 | — | Nov 2, 2022 | 1405d ago | 1.25.4 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
