JetBrains TeamCity End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all JetBrains TeamCity versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2022.04 | 2022.04.7 | Apr 28, 2022 | May 26, 2023 | 1170 days past EOL | EOL |
| 2022.10 | 2022.10.6 | Oct 27, 2022 | Nov 28, 2023 | 984 days past EOL | EOL |
| 2023.05 | 2023.05.6 | May 26, 2023 | Mar 27, 2024 | 864 days past EOL | EOL |
| 2023.11 | 2023.11.5 | Nov 28, 2023 | Jul 18, 2024 | 751 days past EOL | EOL |
| 2024.03 | 2024.03.3 | Mar 27, 2024 | Dec 5, 2024 | 611 days past EOL | EOL |
| 2024.07 | 2024.07.3 | Jul 18, 2024 | Mar 20, 2025 | 506 days past EOL | EOL |
| 2024.12 | 2024.12.3 | Dec 5, 2024 | Jul 23, 2025 | 381 days past EOL | EOL |
| 2025.03 | 2025.03.3 | Mar 20, 2025 | Nov 27, 2025 | 254 days past EOL | EOL |
| 2025.07 | 2025.07.3 | Jul 23, 2025 | May 11, 2026 | 89 days past EOL | EOL |
| 2025.11 | 2025.11.7 | Nov 27, 2025 | TBD | Supported | Active |
| 2026.1 | 2026.1.3 | May 11, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/teamcity)
JetBrains TeamCity lifecycle status — the real story
JetBrains TeamCity On-Premises ships two to three major releases a year under year-based version numbers (2025.11, 2026.1), and JetBrains publishes no end-of-life dates at all — the lifecycle is event-driven. Per the official release cycle policy, bugfix and security patches stop at 'End of Sale', which 'occurs for the previous major version with the release of the next major version', and technical support ends at 'End of Support', which 'occurs with the release of two newer major versions'. The EOL dates in this table are therefore derived: each is the vendor-published release date of the second-following major version, not a date JetBrains ever printed.
In practice JetBrains occasionally reaches past those boundaries for critical security issues — in May 2024 it shipped one-off patched builds for the long-dead 2022.04, 2022.10, and 2023.05 lines, and in July 2026 the previous major 2025.11 received a fixed build alongside the current release. Treat that as an exception, not a promise: the policy explicitly says that after End of Sale 'no bugfix updates or patches are usually provided'.
The urgency is CVE-2026-63077, an unauthenticated remote-code-execution flaw added to CISA's KEV catalog in August 2026 with a federal remediation deadline of August 8: JetBrains states all TeamCity On-Premises versions are affected, fixed builds exist only for 2026.1 (2026.1.3) and 2025.11 (2025.11.7), and every older line gets at best a mitigation plugin for TeamCity 2017.1+ — anything before 2017.1 has no remedy but upgrading.
What does JetBrains TeamCity end of life mean for your organization?
When a version of JetBrains TeamCity 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 JetBrains TeamCity 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 JetBrains TeamCity 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.
| Option | Best when | Watch 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 JetBrains TeamCity versions. This is a bridge, not a permanent solution — plan your migration in parallel.
JetBrains TeamCity has 9 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for JetBrains TeamCity 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.