Coder End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Coder versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.7 | 2.7.3 | Jan 1, 2024 | Apr 3, 2024 | 811 days past EOL | EOL |
| 2.8 | 2.8.5 | Feb 6, 2024 | May 7, 2024 | 777 days past EOL | EOL |
| 2.9 | 2.9.4 | Mar 7, 2024 | Jun 4, 2024 | 749 days past EOL | EOL |
| 2.10 | 2.10.3 | Apr 3, 2024 | Jul 2, 2024 | 721 days past EOL | EOL |
| 2.11 | 2.11.4 | May 7, 2024 | Aug 6, 2024 | 686 days past EOL | EOL |
| 2.12 | 2.12.6 | Jun 4, 2024 | Sep 3, 2024 | 658 days past EOL | EOL |
| 2.13 | 2.13.5 | Jul 2, 2024 | Oct 1, 2024 | 630 days past EOL | EOL |
| 2.14 | 2.14.4 | Aug 6, 2024 | Nov 5, 2024 | 595 days past EOL | EOL |
| 2.15 | 2.15.4 | Sep 3, 2024 | Dec 3, 2024 | 567 days past EOL | EOL |
| 2.16 | 2.16.1 | Oct 1, 2024 | Feb 4, 2025 | 504 days past EOL | EOL |
| 2.17 | 2.17.3 | Nov 5, 2024 | Mar 5, 2025 | 475 days past EOL | EOL |
| 2.18 | 2.18.5 | Dec 3, 2024 | Apr 1, 2025 | 448 days past EOL | EOL |
| 2.19 | 2.19.3 | Feb 4, 2025 | May 16, 2025 | 403 days past EOL | EOL |
| 2.20 | 2.20.3 | Mar 5, 2025 | Jun 3, 2025 | 385 days past EOL | EOL |
| 2.21 | 2.21.3 | Apr 1, 2025 | Jul 1, 2025 | 357 days past EOL | EOL |
| 2.22 | 2.22.1 | May 16, 2025 | Aug 5, 2025 | 322 days past EOL | EOL |
| 2.23 | 2.23.5 | Jun 3, 2025 | Sep 3, 2025 | 293 days past EOL | EOL |
| 2.24 | 2.24.6 | Jul 1, 2025 | Oct 7, 2025 | 259 days past EOL | EOL |
| 2.25 | 2.25.3 | Aug 5, 2025 | Nov 4, 2025 | 231 days past EOL | EOL |
| 2.26 | 2.26.6 | Sep 3, 2025 | Dec 2, 2025 | 203 days past EOL | EOL |
| 2.27 | 2.27.11 | Oct 7, 2025 | Feb 3, 2026 | 140 days past EOL | EOL |
| 2.28 | 2.28.11 | Nov 4, 2025 | Feb 23, 2026 | 120 days past EOL | EOL |
| 2.29 | 2.29.18 | Dec 2, 2025 | Apr 14, 2026 | 70 days past EOL | EOL |
| 2.30 | 2.30.9 | Feb 3, 2026 | May 6, 2026 | 48 days past EOL | EOL |
| 2.31 | 2.31.14 | Mar 3, 2026 | Jun 2, 2026 | 21 days past EOL | EOL |
| 2.32 | 2.32.8 | Apr 14, 2026 | TBD | Supported | Active |
| 2.33 | 2.33.9 | May 6, 2026 | TBD | Supported | Active |
| 2.34 | 2.34.3 | Jun 2, 2026 | TBD | Supported | Active |
What does Coder end of life mean for your organization?
When a version of Coder 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 Coder 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 Coder 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 →