Synced 07 Nov 2026 15:45 UTC Account
← Qt

Qt vulnerabilities: known CVEs & security history

The Qt Company · Dev / Framework · 5 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Qt release lines — 5 in total. A CVE here doesn't mean your version is affected — check Qt's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known Qt CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2023-51714 critical 9.8 1% 2023
CVE-2020-24742 high 7.8 1% 2021
CVE-2021-38593 high 7.5 3% 2021
CVE-2020-0570 high 7.3 1% 2020
CVE-2025-5683 medium 5.5 0% 2025

Is my Qt version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Qt version → · Monitor Qt for new CVEs →

Qt vulnerabilities — frequently asked

How many known vulnerabilities does Qt have?

IsItPatched tracks 5 CVEs for Qt. 1 is critical-severity and 3 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Qt have any actively-exploited vulnerabilities?

None of Qt's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Qt vulnerability?

Among tracked issues, CVE-2023-51714 (CRITICAL, CVSS 9.8) ranks highest — a Integer overflow weakness.

Is Qt safe to use?

It depends on the version. The latest supported Qt release (6.12.0) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Qt security status · Qt end-of-life · actively-exploited CVEs. Always verify against The Qt Company's advisories — see our disclaimer.