Fluent Bit End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Fluent Bit versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.10 | 0.10.1 | Dec 30, 2016 | No EOL date | Supported | Active |
| 0.11 | 0.11.17 | Mar 30, 2017 | No EOL date | Supported | Active |
| 0.12 | 0.12.19 | Aug 17, 2017 | No EOL date | Supported | Active |
| 0.13 | 0.13.8 | Aug 18, 2018 | No EOL date | Supported | Active |
| 0.14 | 0.14.9 | Aug 29, 2018 | No EOL date | Supported | Active |
| 1.0 | 1.0.6 | Dec 13, 2018 | No EOL date | Supported | Active |
| 1.1 | 1.1.3 | May 8, 2019 | No EOL date | Supported | Active |
| 1.2 | 1.2.2 | Jun 26, 2019 | No EOL date | Supported | Active |
| 1.3 | 1.3.11 | Sep 30, 2019 | No EOL date | Supported | Active |
| 1.4 | 1.4.6 | Mar 25, 2020 | No EOL date | Supported | Active |
| 1.5 | 1.5.7 | Jul 13, 2020 | No EOL date | Supported | Active |
| 1.6 | 1.6.10 | Oct 8, 2020 | No EOL date | Supported | Active |
| 1.7 | 1.7.9 | Feb 14, 2021 | No EOL date | Supported | Active |
| 1.8 | 1.8.15 | Jul 7, 2021 | Dec 5, 2022 | 1296 days past EOL | EOL |
| 1.9 | 1.9.10 | Mar 11, 2022 | Dec 5, 2022 | 1296 days past EOL | EOL |
| 2.0 | 2.0.14 | Oct 25, 2022 | Jul 19, 2023 | 1070 days past EOL | EOL |
| 2.1 | 2.1.10 | Apr 18, 2023 | Feb 6, 2024 | 868 days past EOL | EOL |
| 2.2 | 2.2.3 | Nov 6, 2023 | Jun 21, 2024 | 732 days past EOL | EOL |
| 3.0 | 3.0.7 | Mar 21, 2024 | Oct 8, 2024 | 623 days past EOL | EOL |
| 3.1 | 3.1.10 | Jul 8, 2024 | Feb 12, 2025 | 496 days past EOL | EOL |
| 3.2 | 3.2.10 | Nov 12, 2024 | Jun 29, 2025 | 359 days past EOL | EOL |
| 4.0 | 4.0.14 | Mar 29, 2025 | Dec 24, 2025 | 181 days past EOL | EOL |
| 4.1 | 4.1.2 | Sep 24, 2025 | Feb 11, 2026 | 132 days past EOL | EOL |
| 4.2 | 4.2.5 | Nov 11, 2025 | Jun 30, 2026 | 7 days remaining | Warning |
| 5.0 | 5.0.7 | Mar 31, 2026 | TBD | Supported | Active |
What does Fluent Bit end of life mean for your organization?
When a version of Fluent Bit 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 Fluent Bit 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Fluent Bit versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →