Consul End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Consul versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.6 | 1.6.10 | Aug 23, 2019 | Nov 24, 2020 | 2037 days past EOL | EOL |
| 1.7 | 1.7.14 | Feb 11, 2020 | Jun 22, 2021 | 1827 days past EOL | EOL |
| 1.8 | 1.8.19 | Jun 18, 2020 | Dec 14, 2021 | 1652 days past EOL | EOL |
| 1.9 | 1.9.17 | Nov 24, 2020 | Apr 19, 2022 | 1526 days past EOL | EOL |
| 1.10 | 1.10.12 | Jun 22, 2021 | Aug 9, 2022 | 1414 days past EOL | EOL |
| 1.11 | 1.11.11 | Dec 14, 2021 | Nov 15, 2022 | 1316 days past EOL | EOL |
| 1.12 | 1.12.9 | Apr 19, 2022 | Feb 23, 2023 | 1216 days past EOL | EOL |
| 1.13 | 1.13.9 | Aug 9, 2022 | Jun 26, 2023 | 1093 days past EOL | EOL |
| 1.14 | 1.14.11 | Nov 15, 2022 | Nov 3, 2023 | 963 days past EOL | EOL |
| 1.15 | 1.15.11 | Feb 23, 2023 | Feb 27, 2024 | 847 days past EOL | EOL |
| 1.16 | 1.16.7 | Jun 26, 2023 | Jun 12, 2024 | 741 days past EOL | EOL |
| 1.17 | 1.17.4 | Nov 3, 2023 | Oct 14, 2024 | 617 days past EOL | EOL |
| 1.18 | 1.18.2 | Feb 26, 2024 | May 6, 2025 | 413 days past EOL | EOL |
| 1.19 | 1.19.2 | Jun 12, 2024 | Oct 27, 2025 | 239 days past EOL | EOL |
| 1.20 | 1.20.6 | Oct 14, 2024 | May 24, 2026 | 30 days past EOL | EOL |
| 1.21 | 1.21.5 | May 6, 2025 | TBD | Supported | Active |
| 1.22 | 1.22.7 | Oct 27, 2025 | TBD | Supported | Active |
| 2.0 | 2.0.1 | May 24, 2026 | TBD | Supported | Active |
What does Consul end of life mean for your organization?
When a version of Consul 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 Consul 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 Consul 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 →