# CVE-2026-15037: Qt XML XML injection in QDom serialization

Source: https://junglewise.ai/threats/cve-2026-15037-qt-xml-xml-injection-in-qdom-serialization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-23. Updated: 2026-07-23  
License: CC BY 4.0 with a link back

CVE-2026-15037 · Severity: info · CVSS 2.9 · Published 2026-07-23

A vulnerability exists in the Qt XML library, a widely used framework for developing cross-platform software applications. When an application uses this library to generate XML files, it may fail to properly clean up special characters in certain data fields. This could allow an attacker to inject malicious data that alters the structure of the XML document, potentially leading to unauthorized data modification or security bypasses in systems that rely on those files.

Vendors: [Qt Group](https://junglewise.ai/threats/vendors/qt-group).

## Quick answers

**Is CVE-2026-15037 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-15037 being exploited in the wild.

**How severe is CVE-2026-15037?** Informational severity, with a CVSS score of 2.9, published 23 July 2026.

**Which products and versions are affected?** Qt Group Qt XML 4.0.0 through 6.11.x.

**Is there a fix for CVE-2026-15037?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-15037 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-15037?** Check whether you run Qt Group Qt XML at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An XML injection vulnerability (CWE-91) exists in the QDom component of Qt XML due to improper output neutralization during serialization. Specifically, when using the default InvalidDataPolicy (AcceptInvalidChars), the library fails to escape node terminators for comments, CDATA sections, and processing instructions. An attacker providing crafted input to an application that serializes this data can inject arbitrary XML elements or attributes into the resulting document. This affects Qt versions 4.0.0 through 6.11 and is addressed in version 6.12.

## Affected products

- Qt Group Qt XML 4.0.0 through 6.11.x

## Timeline

- 2026-07-23: disclosed
- 2026-07-23: advisory

## References

- [https://codereview.qt-project.org/c/qt/qtbase/+/748323](https://codereview.qt-project.org/c/qt/qtbase/+/748323)