Influxdb End of Life Dates
other
Developers rely on time-series databases like Influxdb to efficiently store and manage large amounts of data, and Influxdb has been a popular choice since its creation. Maintained by a community of developers, Influxdb has been widely adopted due to its scalability and flexibility, allowing developers to handle high-volume data streams with ease. With a long history dating back to its inception, Influxdb has become a staple in many development environments, providing a robust solution for data management and analytics.
Influxdb has a complex version landscape, with a total of 12 versions released over time, out of which 8 have reached their end-of-life. Currently, there are 4 active versions that are still supported, with the latest stable version being 2.9.1. The most recent version to reach end-of-life was 3.7, which occurred on 2026-04-02, and there is no announced date for the next version to expire. This information is crucial for developers who need to plan their upgrades and ensure they are running supported versions of Influxdb to avoid potential security risks and compatibility issues.
The security picture for Influxdb is currently stable, with no known Common Vulnerabilities and Exposures (CVEs) tracked, and therefore no critical CVEs. As a result, there is no most affected version, and Influxdb is not listed on the Known Exploited Vulnerabilities (KEV) catalog. Given this information, developers can continue to use Influxdb with confidence, but it is still essential to keep their versions up to date and monitor the official Influxdb channels for any future security announcements or updates to ensure the continued security and integrity of their systems.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.10 | Jun 17, 2026 | — | No | — | 3.10.5 | — | Active | |
| 3.9 | Apr 2, 2026 | — | No | — | 3.9.11 | — | Active | |
| 3.8 | Dec 18, 2025 | — | Jun 17, 2026 | 37d ago | 3.8.3 | — | EOL | |
| 3.7 | Nov 19, 2025 | — | Apr 2, 2026 | 113d ago | 3.7.0 | — | EOL | |
| 3.6 | Oct 30, 2025 | — | Dec 18, 2025 | 218d ago | 3.6.0 | — | EOL | |
| 3.5 | Sep 29, 2025 | — | Nov 19, 2025 | 247d ago | 3.5.0 | — | EOL | |
| 3.4 | Aug 26, 2025 | — | Oct 30, 2025 | 267d ago | 3.4.2 | — | EOL | |
| 3.3 | Jul 29, 2025 | — | Sep 29, 2025 | 298d ago | 3.3.0 | — | EOL | |
| 3.2 | Jun 25, 2025 | — | Aug 26, 2025 | 332d ago | 3.2.1 | — | EOL | |
| 3.1 | May 28, 2025 | — | Jul 30, 2025 | 359d ago | 3.1.0 | — | EOL | |
| 3.0 | Apr 14, 2025 | — | Jun 25, 2025 | 394d ago | 3.0.3 | — | EOL | |
| 2 | Nov 9, 2020 | — | No | — | 2.9.1 | — | Active | |
| 1 | Sep 7, 2016 | — | No | — | 1.12.4 | — | Active |
Data sourced from endoflife.date · CVE data from NVD
