CVE-2025-5683

CVE-2025-5683 is a medium-severity vulnerability in Qt with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Description

When loading a specifically crafted ICNS format image file in QImage then it will trigger a crash. This issue affects Qt from versions 6.3.0 through 6.5.9, from 6.6.0 through 6.8.4, 6.9.0. This is fixed in 6.5.10, 6.8.5 and 6.9.1.

Frequently asked questions

What is CVE-2025-5683?
When loading a specifically crafted ICNS format image file in QImage then it will trigger a crash. This issue affects Qt from versions 6.3.0 through 6.5.9, from 6.6.0 through 6.8.4, 6.9.0. This is fixed in 6.5.10, 6.8.5 and 6.9.1.
How severe is CVE-2025-5683?
CVE-2025-5683 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-5683 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-5683?
CVE-2025-5683 affects Qt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-5683?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-5683 have an EU (EUVD) identifier?
Yes. CVE-2025-5683 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16968.
When was CVE-2025-5683 published?
CVE-2025-5683 was published on 2025-06-05 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Qt

All CVEs affecting Qt →

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →