JetBrains TeamCity End of Life (EOL) Dates & Support Timeline

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.

JetBrains TeamCity release and support pattern

Across the 12 release lines with a published release date, JetBrains TeamCity has shipped a new line roughly every 4 months (median interval). A line typically stays supported for about 9 months from its release to its end-of-life date (measured on the 10 lines with both dates published).

Of the 12 release lines tracked, 10 are past end of life and 2 are still within support. The newest line, 2026.2, was released September 2, 2026. No end-of-life date is currently published for the 2 supported lines.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

JetBrains TeamCity security intelligence

CISA KEV history: JetBrains TeamCity is named in CISA's Known Exploited Vulnerabilities catalog 4 times, most recently on 2026-08-05, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

Patch behavior after end of life: Hard cutoff — supported versions only. JetBrains ships security fixes for the current and immediately previous release lines only. For KEV-listed CVE-2026-63077 the fix exists solely in 2025.11.7 and 2026.1.3 — nine earlier lines listed as affected received nothing, consistent with JetBrains' published policy. (Observed behavior from our primary-source verification sweep, checked 2026-08-07 — never a guarantee of future fixes.)

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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.

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.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

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.

Related Products