Qt 6.12 · Version Status

Qt 6.12 End of Life Date

Qt 6.12 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Qt 6.12 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
6.12.0
LTS release
Release Date
Sep 30, 2026
Qt 6.12 series
Extended Support
Sep 30, 2031
Qt commercial standard support · paid
Lifecycle detail

Qt 6.12 was released on September 30, 2026 and has no published end-of-life date yet. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 6.12.0, published September 30, 2026.

← Qt 6.11 All Qt versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Qt Versions
VersionLatestEOL DateStatus
4.8 LTS 4.8.7 Dec 31, 2015 EOL
5.6 LTS 5.6.3 Mar 16, 2019 EOL
5.9 5.9.9 May 31, 2020 EOL
5.12 LTS 5.12.12 Dec 5, 2021 EOL
5.13 5.13.2 Jun 19, 2020 EOL
5.14 5.14.2 Dec 12, 2020 EOL
5.15 LTS 5.15.17 Dec 8, 2020 EOL
6.0 6.0.4 May 5, 2021 EOL

What does Qt 6.12 end of life mean?

When Qt 6.12 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Qt 6.12 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Qt 6.12 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Qt 6.12 reach end of life?
Qt 6.12 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Qt 6.12 still supported?
Yes, Qt 6.12 is currently supported. The EOL date is TBD.
What should I upgrade to from Qt 6.12?
The recommended upgrade from Qt 6.12 is Qt 6.12 — the latest actively supported version. Check the Qt full timeline for all supported versions.
What are the security risks of running Qt 6.12 past EOL?
When Qt 6.12 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Qt should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →