Coder · Lifecycle Status

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.

Coder 2.36.0 is actively supported. No versions approaching EOL in the next 6 months.
Running an EOL version? Get matched with support options — free ↓
Latest Active
2.36.0
2.36 series
Next EOL
None upcoming
Active Versions
3
of 30 total
EOL Versions
27
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 2024202520262.72.82.92.102.112.122.132.142.152.162.172.182.192.202.212.222.232.242.252.262.272.282.292.302.312.322.332.342.352.36TODAY
27 versions of Coder are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
2.7 2.7.3 Jan 1, 2024 Apr 3, 2024 858 days past EOL EOL
2.8 2.8.5 Feb 6, 2024 May 7, 2024 824 days past EOL EOL
2.9 2.9.4 Mar 7, 2024 Jun 4, 2024 796 days past EOL EOL
2.10 2.10.3 Apr 3, 2024 Jul 2, 2024 768 days past EOL EOL
2.11 2.11.4 May 7, 2024 Aug 6, 2024 733 days past EOL EOL
2.12 2.12.6 Jun 4, 2024 Sep 3, 2024 705 days past EOL EOL
2.13 2.13.5 Jul 2, 2024 Oct 1, 2024 677 days past EOL EOL
2.14 2.14.4 Aug 6, 2024 Nov 5, 2024 642 days past EOL EOL
2.15 2.15.4 Sep 3, 2024 Dec 3, 2024 614 days past EOL EOL
2.16 2.16.1 Oct 1, 2024 Feb 4, 2025 551 days past EOL EOL
2.17 2.17.3 Nov 5, 2024 Mar 5, 2025 522 days past EOL EOL
2.18 2.18.5 Dec 3, 2024 Apr 1, 2025 495 days past EOL EOL
2.19 2.19.3 Feb 4, 2025 May 16, 2025 450 days past EOL EOL
2.20 2.20.3 Mar 5, 2025 Jun 3, 2025 432 days past EOL EOL
2.21 2.21.3 Apr 1, 2025 Jul 1, 2025 404 days past EOL EOL
2.22 2.22.1 May 16, 2025 Aug 5, 2025 369 days past EOL EOL
2.23 2.23.5 Jun 3, 2025 Sep 3, 2025 340 days past EOL EOL
2.24 LTS 2.24.6 Jul 1, 2025 Oct 7, 2025 Jul 1, 2026
Extended support (ended)
306 days past EOL EOL
2.25 2.25.3 Aug 5, 2025 Nov 4, 2025 278 days past EOL EOL
2.26 2.26.6 Sep 3, 2025 Dec 2, 2025 250 days past EOL EOL
2.27 2.27.11 Oct 7, 2025 Feb 3, 2026 187 days past EOL EOL
2.28 2.28.11 Nov 4, 2025 Feb 23, 2026 167 days past EOL EOL
2.29 LTS 2.29.19 Dec 2, 2025 Apr 14, 2026 Dec 2, 2026
Extended support
117 days past EOL EOL
2.30 2.30.9 Feb 3, 2026 May 6, 2026 95 days past EOL EOL
2.31 2.31.14 Mar 3, 2026 Jun 2, 2026 68 days past EOL EOL
2.32 2.32.10 Apr 14, 2026 Jul 7, 2026 33 days past EOL EOL
2.33 2.33.11 May 6, 2026 Aug 4, 2026 5 days past EOL EOL
2.34 LTS 2.34.7 Jun 2, 2026 TBD Jun 2, 2027
Extended support
Supported Active
2.35 2.35.3 Jul 7, 2026 TBD Supported Active
2.36 2.36.0 Aug 4, 2026 TBD Supported Active
EOL date vs extended support. The EOL Date column is the end of standard, included support. Extended support terms vary by vendor. Check whether the programme covers you before relying on these dates. 1 version of Coder is past the standard EOL date but still inside the extended support window.
Coder EOL status badge Live EOL badge for your README — updates automatically at every build. [![Coder EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fcoder.json)](https://endoflife.ai/coder)

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.

Your options when Coder reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

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.

endoflife.ai
Get Coder Support Options

Coder has 27 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Coder exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Coder?
See the full table above for all Coder version EOL dates.
When is the Coder support end date?
Each Coder version has its own support end date — see the table above for every version's date.
What is the latest supported version of Coder?
The latest active version of Coder is 2.36.0. Always verify against the table above as support windows can change.
What happens when Coder reaches end of life?
When Coder 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 Coder?
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 Coder 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 →
Coder end-of-life status badge