tvOS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all tvOS versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
tvOS 27 is supported, with no end-of-life or end-of-support date announced yet. 11 of 12 tracked tvOS versions are past end of life; the most recent to reach it, 26, did so on September 14, 2026. The full tvOS lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9 | 9.2.2 | Oct 29, 2015 | Sep 13, 2016 | 3662 days past EOL | EOL |
| 10 | 10.2.2 | Sep 13, 2016 | Sep 19, 2017 | 3291 days past EOL | EOL |
| 11 | 11.4.1 | Sep 19, 2017 | Sep 17, 2018 | 2928 days past EOL | EOL |
| 12 | 12.4.1 | Sep 17, 2018 | Sep 24, 2019 | 2556 days past EOL | EOL |
| 13 | 13.4.8 | Sep 24, 2019 | Sep 16, 2020 | 2198 days past EOL | EOL |
| 14 | 14.7 | Sep 16, 2020 | Sep 20, 2021 | 1829 days past EOL | EOL |
| 15 | 15.6 | Sep 20, 2021 | Sep 12, 2022 | 1472 days past EOL | EOL |
| 16 | 16.6 | Sep 12, 2022 | Sep 18, 2023 | 1101 days past EOL | EOL |
| 17 | 17.6.1 | Sep 18, 2023 | Sep 16, 2024 | 737 days past EOL | EOL |
| 18 | 18.6 | Sep 16, 2024 | Sep 15, 2025 | 373 days past EOL | EOL |
| 26 | 26.6 | Sep 15, 2025 | Sep 14, 2026 | 9 days past EOL | EOL |
| 27 | 27 | Sep 14, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/tvos)
tvOS release and support pattern
Across the 12 release lines with a published release date, tvOS has shipped a new line roughly every 1 year (median interval). A line typically stays supported for about 1 year from its release to its end-of-life date (measured on the 11 lines with both dates published).
Of the 12 release lines tracked, 11 are past end of life and 1 is still within support. The newest line, 27, was released September 14, 2026. No end-of-life date is currently published for the 1 supported line.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does tvOS end of life mean for your organization?
When a version of tvOS 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 tvOS 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 tvOS 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 |
| Commercial extended support | Not available for tvOS from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →