Telegraf 1.36 · Version Status
Telegraf 1.36 End of Life Date
Telegraf 1.36 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Telegraf 1.36 is past end of life. This version no longer receives security patches. 61 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 9, 2026
61 days past EOL
Latest Release
1.36.4
Standard release
Release Date
Sep 8, 2025
Telegraf 1.36 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.1 |
Jan 23, 2017 |
EOL |
| 1.1 |
1.1.2 |
May 15, 2017 |
EOL |
| 1.2 |
1.2.1 |
Sep 5, 2017 |
EOL |
| 1.3 |
1.3.5 |
Dec 14, 2017 |
EOL |
| 1.4 |
1.4.5 |
Apr 16, 2018 |
EOL |
| 1.5 |
1.5.3 |
Jun 12, 2018 |
EOL |
| 1.6 |
1.6.4 |
Sep 21, 2018 |
EOL |
| 1.7 |
1.7.4 |
Nov 20, 2018 |
EOL |
What does Telegraf 1.36 end of life mean?
When Telegraf 1.36 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Telegraf 1.36 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Telegraf 1.38 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Telegraf 1.36 reach end of life?
Telegraf 1.36 reached end of life on March 9, 2026. This version is no longer receiving security patches.
Is Telegraf 1.36 still supported?
No. Telegraf 1.36 reached end of life on March 9, 2026 and is no longer receiving security patches.
What should I upgrade to from Telegraf 1.36?
The recommended upgrade from Telegraf 1.36 is
Telegraf 1.38 — the latest actively supported version. Check the
Telegraf full timeline for all supported versions.
What are the security risks of running Telegraf 1.36 past EOL?
When Telegraf 1.36 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Telegraf should migrate immediately or implement compensating controls.