Telegraf · Lifecycle Status

Telegraf End of Life (EOL) Dates & Support Timeline

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

Telegraf 1.39.0 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.39.0
1.39 series
Next EOL
None upcoming
Active Versions
2
of 40 total
EOL Versions
38
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20172018201920202021202220232024202520261.01.11.21.31.41.51.61.71.81.91.101.111.121.131.141.151.161.171.181.191.201.211.221.231.241.251.261.271.281.291.301.311.321.331.341.351.361.371.381.39TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.0 1.0.1 Sep 2, 2016 Jan 23, 2017 3438 days past EOL EOL
1.1 1.1.2 Nov 8, 2016 May 15, 2017 3326 days past EOL EOL
1.2 1.2.1 Jan 23, 2017 Sep 5, 2017 3213 days past EOL EOL
1.3 1.3.5 May 15, 2017 Dec 14, 2017 3113 days past EOL EOL
1.4 1.4.5 Sep 5, 2017 Apr 16, 2018 2990 days past EOL EOL
1.5 1.5.3 Dec 14, 2017 Jun 12, 2018 2933 days past EOL EOL
1.6 1.6.4 Apr 16, 2018 Sep 21, 2018 2832 days past EOL EOL
1.7 1.7.4 Jun 12, 2018 Nov 20, 2018 2772 days past EOL EOL
1.8 1.8.3 Sep 21, 2018 Mar 5, 2019 2667 days past EOL EOL
1.9 1.9.5 Nov 20, 2018 Jun 11, 2019 2569 days past EOL EOL
1.10 1.10.4 Mar 5, 2019 Sep 3, 2019 2485 days past EOL EOL
1.11 1.11.5 Jun 11, 2019 Dec 12, 2019 2385 days past EOL EOL
1.12 1.12.6 Sep 3, 2019 Mar 26, 2020 2280 days past EOL EOL
1.13 1.13.4 Dec 12, 2019 Jul 22, 2020 2162 days past EOL EOL
1.14 1.14.5 Mar 26, 2020 Oct 21, 2020 2071 days past EOL EOL
1.15 1.15.4 Jul 22, 2020 Dec 18, 2020 2013 days past EOL EOL
1.16 1.16.3 Oct 21, 2020 Mar 17, 2021 1924 days past EOL EOL
1.17 1.17.3 Dec 18, 2020 Jun 17, 2021 1832 days past EOL EOL
1.18 1.18.3 Mar 17, 2021 Sep 17, 2021 1740 days past EOL EOL
1.19 1.19.3 Jun 17, 2021 Dec 15, 2021 1651 days past EOL EOL
1.20 1.20.4 Sep 17, 2021 Mar 23, 2022 1553 days past EOL EOL
1.21 1.21.4 Dec 15, 2021 Jun 13, 2022 1471 days past EOL EOL
1.22 1.22.4 Mar 23, 2022 Sep 12, 2022 1380 days past EOL EOL
1.23 1.23.4 Jun 13, 2022 Dec 12, 2022 1289 days past EOL EOL
1.24 1.24.4 Sep 12, 2022 Mar 13, 2023 1198 days past EOL EOL
1.25 1.25.3 Dec 12, 2022 Jun 12, 2023 1107 days past EOL EOL
1.26 1.26.3 Mar 13, 2023 Sep 11, 2023 1016 days past EOL EOL
1.27 1.27.4 Jun 12, 2023 Dec 11, 2023 925 days past EOL EOL
1.28 1.28.5 Sep 11, 2023 Mar 11, 2024 834 days past EOL EOL
1.29 1.29.5 Dec 11, 2023 Jun 10, 2024 743 days past EOL EOL
1.30 1.30.3 Mar 11, 2024 Sep 9, 2024 652 days past EOL EOL
1.31 1.31.3 Jun 10, 2024 Dec 9, 2024 561 days past EOL EOL
1.32 1.32.3 Sep 9, 2024 Mar 10, 2025 470 days past EOL EOL
1.33 1.33.3 Dec 9, 2024 Jun 16, 2025 372 days past EOL EOL
1.34 1.34.4 Mar 10, 2025 Sep 8, 2025 288 days past EOL EOL
1.35 1.35.4 Jun 16, 2025 Dec 8, 2025 197 days past EOL EOL
1.36 1.36.4 Sep 8, 2025 Mar 9, 2026 106 days past EOL EOL
1.37 1.37.3 Dec 8, 2025 Jun 8, 2026 15 days past EOL EOL
1.38 1.38.4 Mar 9, 2026 TBD Supported Active
1.39 1.39.0 Jun 8, 2026 TBD Supported Active

What does Telegraf end of life mean for your organization?

When a version of Telegraf 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 Telegraf 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 Telegraf versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for Telegraf?
See the full table above for all Telegraf version EOL dates.
When is the Telegraf support end date?
Each Telegraf version has its own support end date — see the table above for every version's date.
What is the latest supported version of Telegraf?
The latest active version of Telegraf is 1.39.0. Always verify against the table above as support windows can change.
What happens when Telegraf reaches end of life?
When Telegraf 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 Telegraf?
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 Telegraf 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 →