# CVE-2026-11573: Uncontrolled recursion in QDomDocument/QDomNode serialization causes stack exhaustion (QtXml) > Attackers can cause application crashes via stack exhaustion by providing deeply nested XML documents to the Qt XML module for serialization. - **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 8 Sep 2026 - **Updated:** 11 Sep 2026 - **Also known as:** AZL-100947, DEBIAN-CVE-2026-11573, ECHO-c835-5b93-7765, GHSA-m72v-p257-4w4p, OESA-2026-4495, OESA-2026-4496, OESA-2026-4612, RHSA-2026:74653, RHSA-2026:84582, UBUNTU-CVE-2026-11573 ## What is CVE-2026-11573? CVE-2026-11573 is a high-severity denial of service vulnerability in qt, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2026-11573? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qt6-qtbase` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-common` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-devel-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-examples` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-examples-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-gui` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-gui-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-mysql` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-mysql-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-odbc` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-odbc-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-postgresql` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-postgresql-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-private-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-static` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase-tests-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-9.el10_0.1 | | `qt6-qtbase` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-common` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-devel` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-examples` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-gui` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-ibase` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-mysql` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-odbc` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-postgresql` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-private-devel` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | | `qt6-qtbase-static` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-3.hum1 | ## How do I fix CVE-2026-11573? Apply the vendor's patch. ## Is CVE-2026-11573 being exploited? There is no known exploitation of CVE-2026-11573 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-11573 and fix it if it is affected. What it is: CVE-2026-11573 is a high-severity denial of service vulnerability in qt, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-11573 in the wild and no public exploit code. Affected product: qt. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-11573/ (Markdown: https://insights.sbomify.com/CVE-2026-11573/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11573 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11573 - OSV: https://osv.dev/vulnerability/CVE-2026-11573 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-11573/ Summaries are generated and may contain mistakes; the official description above is the record.