Qt End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Qt versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.8 LTS | 4.8.7 | Dec 15, 2011 | Dec 31, 2015 | 3827 days past EOL | EOL |
| 5.6 LTS | 5.6.3 | Mar 15, 2016 | Mar 16, 2019 | 2656 days past EOL | EOL |
| 5.9 | 5.9.9 | May 29, 2017 | May 31, 2020 | 2214 days past EOL | EOL |
| 5.12 LTS | 5.12.12 | Dec 4, 2018 | Dec 5, 2021 | 1661 days past EOL | EOL |
| 5.13 | 5.13.2 | Jun 18, 2019 | Jun 19, 2020 | 2195 days past EOL | EOL |
| 5.14 | 5.14.2 | Dec 11, 2019 | Dec 12, 2020 | 2019 days past EOL | EOL |
| 5.15 LTS | 5.15.17 | May 25, 2020 | Dec 8, 2020 | 2023 days past EOL | EOL |
| 6.0 | 6.0.4 | Dec 8, 2020 | May 5, 2021 | 1875 days past EOL | EOL |
| 6.1 | 6.1.3 | May 5, 2021 | Sep 30, 2021 | 1727 days past EOL | EOL |
| 6.2 LTS | 6.2.4 | Sep 30, 2021 | Apr 11, 2022 | 1534 days past EOL | EOL |
| 6.3 | 6.3.2 | Apr 11, 2022 | Sep 28, 2022 | 1364 days past EOL | EOL |
| 6.4 | 6.4.3 | Sep 28, 2022 | Mar 31, 2023 | 1180 days past EOL | EOL |
| 6.5 LTS | 6.5.8 | Mar 31, 2023 | Oct 9, 2023 | 988 days past EOL | EOL |
| 6.6 | 6.6.3 | Oct 9, 2023 | Apr 2, 2024 | 812 days past EOL | EOL |
| 6.7 | 6.7.3 | Mar 28, 2024 | Oct 7, 2024 | 624 days past EOL | EOL |
| 6.8 LTS | 6.8.3 | Oct 7, 2024 | Apr 2, 2025 | 447 days past EOL | EOL |
| 6.9 | 6.9.3 | Apr 2, 2025 | Oct 7, 2025 | 259 days past EOL | EOL |
| 6.10 | 6.10.3 | Oct 7, 2025 | Apr 7, 2026 | 77 days past EOL | EOL |
| 6.11 | 6.11.1 | Mar 23, 2026 | Sep 22, 2026 | 91 days remaining | Warning |
What does Qt end of life mean for your organization?
When a version of Qt 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 Qt 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Qt versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →