Influxdb · Lifecycle Status

Influxdb End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Influxdb versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Influxdb 1.12.4 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.12.4
1 series
Next EOL
None upcoming
Active Versions
4
of 12 total
EOL Versions
8
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2017201820192020202120222023202420252026123.03.13.23.33.43.53.63.73.83.9TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1 1.12.4 Sep 7, 2016 Already EOL Supported Active
2 2.9.0 Nov 9, 2020 Already EOL Supported Active
3.0 3.0.3 Apr 14, 2025 Jun 25, 2025 318 days past EOL EOL
3.1 3.1.0 May 28, 2025 Jul 30, 2025 283 days past EOL EOL
3.2 3.2.1 Jun 25, 2025 Aug 26, 2025 256 days past EOL EOL
3.3 3.3.0 Jul 29, 2025 Sep 29, 2025 222 days past EOL EOL
3.4 3.4.2 Aug 26, 2025 Oct 30, 2025 191 days past EOL EOL
3.5 3.5.0 Sep 29, 2025 Nov 19, 2025 171 days past EOL EOL
3.6 3.6.0 Oct 30, 2025 Dec 18, 2025 142 days past EOL EOL
3.7 3.7.0 Nov 19, 2025 Apr 2, 2026 37 days past EOL EOL
3.8 3.8.3 Dec 18, 2025 Already EOL Supported Active
3.9 3.9.2 Apr 2, 2026 Already EOL Supported Active

What does Influxdb end of life mean for your organization?

When a Influxdb 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 Influxdb 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Influxdb?
See the full table above for all Influxdb version EOL dates.
What is the latest supported version of Influxdb?
The latest active version of Influxdb is 1.12.4. Always verify against the table above as support windows can change.
What happens when Influxdb reaches end of life?
When Influxdb reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Influxdb?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Influxdb versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →