CVE-2026-11573: Uncontrolled recursion in QDomDocument/QDomNode serialization causes stack exhaustion (QtXml)

Published Sep 8, 2026
·
Updated

Uncontrolled recursion (CWE-674) in the QDomDocument/QDomNode serialization path of the Qt XML module (QtXml, qtbase). QDomElementPrivate::save() and QDomNodePrivate::save() recurse mutually, consuming one stack frame per level of element nesting with no depth limit, no configurable bound and no error return. A document with deeply nested elements parses successfully but exhausts the call stack and terminates the process when serialized. Reachable via QDomDocument::toByteArray() (Qt 4.0 and later), QDomDocument::toString(), QDomDocument::toCString(), QDomNode::save(), and operator<<(QTextStream&, const QDomNode&). Denial of service only — no code execution and no memory disclosure.

Other sources

Uncontrolled recursion in QDomDocument/QDomNode serialization causes stack exhaustion (QtXml)

— Microsoft

Affected Software

2 affected componentsFixes available
Qt Qt XML (QtXml, qtbase)
Microsoft azl3 qtbase 6.6.3-5<6.6.3-6
6.6.3-6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.3-6
  2. Compensating control

    Apply a practical limit on how deeply nested XML is accepted/processed before serializing with Qt (e.g., reject or truncate documents whose element nesting depth exceeds a configured threshold), since the Qt QDomDocument/QDomNode serialization path can recurse without a depth limit and exhaust the call stack.

Event History

Sep 8, 2026
CVE Published
via MITRE·12:06 PM
Data Sourced
via MITRE·12:06 PM
DescriptionWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness
Sep 13, 2026
Data Sourced
via Microsoft·08:13 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:13 AM
DescriptionSeverity

Frequently Asked Questions

1

What applications are exposed to this issue?

Applications that use QtXml's QDomDocument to parse and serialize untrusted XML are exposed if an attacker can supply deeply nested XML. The reported impact is an application crash through stack exhaustion.

2

What must an attacker provide to trigger the crash?

The attacker needs to cause the application to process deeply nested untrusted XML and serialize the resulting QDomDocument with toByteArray(). The issue is denial of service only.

3

How can I determine whether an application may be affected?

Review whether the application accepts XML from untrusted sources, uses QDomDocument from QtXml to parse it, and calls QDomDocument::toByteArray() on the parsed document. Deeply nested XML in that processing path is the relevant condition.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203