Unity 2017 End of Life Date
Unity 2017 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
Unity 2017 was released on June 26, 2017 and support ended on May 18, 2020 — a supported lifespan of 2 years and 11 months, in line with the 2 years and 10 months median for Unity LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 2017.4.40f1, published May 18, 2020 — on the day support ended. It has been without security patches for 6 years and 3 months. 16 newer Unity releases have shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 2017 LTS | 2017.4.40f1 | May 18, 2020 | EOL |
| 2018 LTS | 2018.4.36f1 | Jun 17, 2021 | EOL |
| 2019 LTS | 2019.4.41f2 | Jun 16, 2022 | EOL |
| 2020 LTS | 2020.3.49f1 | May 5, 2023 | EOL |
| 2021.1 | 2021.1.29f1 | Nov 4, 2022 | EOL |
| 2021.2 | 2021.2.20f1 | Apr 5, 2022 | EOL |
| 2021.3 | 2021.3.45f2 | Feb 18, 2025 | EOL |
| 2021 LTS | 2021.3.45f2 | Feb 18, 2025 | EOL |
What does Unity 2017 end of life mean?
When Unity 2017 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Unity 2017 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Unity 6.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.