OESA-2026-4911: qt security update
Qt (pronounced as "cute", not "cu-tee") is a cross-platform framework that is usually used as a graphical toolkit, although it is also very helpful in creating CLI applications. It runs on the three major desktop OSes, as well as on mobile OSes, such as Symbian, Nokia Belle, Meego Harmattan, MeeGo or BB10, and on embedded devices. Ports for Android (Necessitas) and iOS are also in development Security Fix(es):
An issue was found in the private API function qDecodeDataUrl() in QtCore, which is used in QTextDocument and QNetworkReply, and, potentially, in user code.
If the function was called with malformed data, for example, an URL that contained a "charset" parameter that lacked a value (such as "data:charset,"), and Qt was built with assertions enabled, then it would hit an assertion, resulting in a denial of service (abort).
This impacts Qt up to 5.15.18, 6.0.0->6.5.8, 6.6.0->6.8.3 and 6.9.0. This has been fixed in 5.15.19, 6.5.9, 6.8.4 and 6.9.1.(CVE-2025-5455)
An attacker able to supply a crafted XML document to an application using QXmlStreamReader can cause disproportionate CPU consumption during parsing, making the application unresponsive (denial of service). Exploitation requires only that the application parse attacker-influenced XML; no authentication, privileges, or user interaction beyond ingesting the input are needed. There is no loss of confidentiality or integrity — no data disclosure, data modification, or code execution — and the impact is contained to the affected process.(CVE-2026-16762)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/qtto a version that resolves this vulnerability.Fixed in 4.8.7-69.oe2403sp3 - Upgrade
Upgrade
Qtto a version that resolves this vulnerability.Fixed in 5.15.19 - Upgrade
Upgrade
Qtto a version that resolves this vulnerability.Fixed in 6.5.9 - Upgrade
Upgrade
Qtto a version that resolves this vulnerability.Fixed in 6.8.4 - Upgrade
Upgrade
Qtto a version that resolves this vulnerability.Fixed in 6.9.1
Event History
Frequently Asked Questions
Which applications are exposed to the data URL denial-of-service issue?
Applications are exposed when they use qDecodeDataUrl() directly or through QTextDocument or QNetworkReply, are built with assertions enabled, and process attacker-supplied malformed data URLs. A data URL with a charset parameter lacking a value, such as data:charset,, can trigger an assertion abort.
What Qt versions are affected by the data URL issue?
The issue affects Qt through 5.15.18, versions 6.0.0 through 6.5.8, versions 6.6.0 through 6.8.3, and 6.9.0. It is fixed in 5.15.19, 6.5.9, 6.8.4, and 6.9.1.
Who is exposed to the XML parsing CPU-consumption issue?
Applications that use QXmlStreamReader to parse XML documents supplied by an attacker are exposed. A crafted XML document can cause disproportionate CPU consumption during parsing, creating a denial-of-service condition.