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.
Metrics
Affected Vendors & Products
References
History
Fri, 06 Jun 2025 22:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-617 |
Tue, 03 Jun 2025 02:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Mon, 02 Jun 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Mon, 02 Jun 2025 09:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | Possible denial of service when passing malformed data in a URL to qDecodeDataUrl | |
Weaknesses | CWE-20 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: TQtC
Published: 2025-06-02T08:46:20.524Z
Updated: 2025-06-02T12:42:34.203Z
Reserved: 2025-06-02T08:31:36.081Z
Link: CVE-2025-5455

Updated: 2025-06-02T12:42:02.535Z

Status : Awaiting Analysis
Published: 2025-06-02T09:15:21.493
Modified: 2025-06-02T17:32:17.397
Link: CVE-2025-5455
