No advisories yet.
Solution
Update to Qt 6.12 or later.
Workaround
On all affected versions, set the invalid-data policy before building documents:QDomImplementation::setInvalidDataPolicy(QDomImplementation::ReturnNullNode); (or DropInvalidChars). With ReturnNullNode, the QDom factory functions return a null node when given data that is invalid per XML 1.0 — check the return value. As additional defence-in-depth, validate untrusted input before inserting it and do not treat QDom output as trusted structure downstream.
| Link | Providers |
|---|---|
| https://codereview.qt-project.org/c/qt/qtbase/+/748323 |
|
Thu, 23 Jul 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 23 Jul 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper output neutralization (XML injection) in QDom comment, CDATA, and processing-instruction serialization in Qt XML from 4.0.0 through 6.11 allows untrusted text serialized by an application into those nodes to inject arbitrary XML markup, because the node terminators are not escaped under the default InvalidDataPolicy (AcceptInvalidChars). Fixed in Qt 6.12. | |
| Title | XML injection vulnerability in QDom comment, CDATA and processing-instruction serialization | |
| First Time appeared |
Qt
Qt qt |
|
| Weaknesses | CWE-91 | |
| CPEs | cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Qt
Qt qt |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: TQtC
Published:
Updated: 2026-07-23T14:45:39.734Z
Reserved: 2026-07-08T08:35:17.940Z
Link: CVE-2026-15037
Updated: 2026-07-23T14:45:35.678Z
No data.
No data.
OpenCVE Enrichment
No data.