Quick answers
- Is CVE-2026-11573 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11573 being exploited in the wild.
- How severe is CVE-2026-11573?
- Informational severity, with a CVSS score of 0, published 8 September 2026.
- Which products and versions are affected?
- The Qt Company QtXml Qt 4.0 and later.
- Is there a fix for CVE-2026-11573?
- 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-11573 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-11573?
- Check whether you run The Qt Company QtXml 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
The vulnerability is an uncontrolled recursion (CWE-674) in the QDomDocument/QDomNode serialization path of the Qt XML module. QDomElementPrivate::save() and QDomNodePrivate::save() recurse mutually without enforcing any depth limit or configurable recursion bound, consuming one stack frame per element nesting level. A document with deeply nested elements parses successfully but causes stack exhaustion during serialization via QDomDocument::toByteArray(), toString(), toCString(), QDomNode::save(), or the << operator with QTextStream. The attack is reachable from any code that serializes user-controlled or untrusted XML, requiring only that the application call one of the affected serialization methods. This is a denial of service issue with no code execution or memory disclosure.
Affected products
- The Qt Company QtXml Qt 4.0 and later
Timeline
- 2026-09-08: disclosed