Complete end-of-life dates, support windows, and security status for all Flux versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.25 | 1.25.4 | Mar 30, 2022 | Nov 2, 2022 | 1284 days past EOL | EOL |
| 2.0 | 2.0.1 | Jul 5, 2023 | May 13, 2024 | 726 days past EOL | EOL |
| 2.1 | 2.1.2 | Aug 24, 2023 | Sep 30, 2024 | 586 days past EOL | EOL |
| 2.2 | 2.2.3 | Dec 12, 2023 | Feb 20, 2025 | 443 days past EOL | EOL |
| 2.3 | 2.3.0 | May 13, 2024 | May 29, 2025 | 345 days past EOL | EOL |
| 2.4 | 2.4.0 | Sep 30, 2024 | Sep 30, 2025 | 221 days past EOL | EOL |
| 2.5 | 2.5.1 | Feb 20, 2025 | Feb 24, 2026 | 74 days past EOL | EOL |
| 2.6 | 2.6.4 | May 29, 2025 | Already EOL | Supported | Active |
| 2.7 | 2.7.5 | Sep 30, 2025 | Already EOL | Supported | Active |
| 2.8 | 2.8.6 | Feb 24, 2026 | Already EOL | Supported | Active |
When a Flux version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Flux should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →