# CVE-2025-10728: Uncontrolled recursion in Qt SVG module

> An attacker can cause a stack overflow and denial of service by providing a crafted SVG file with recursive pattern elements to applications using the Qt SVG module.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:P/RE:H/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Oct 2025
- **Updated:** 29 Jul 2026
- **Also known as:** ALSA-2025:22394, DEBIAN-CVE-2025-10728, GHSA-x6f6-j278-6544, RHSA-2025:22393, RHSA-2025:22394, RLSA-2025:22394, UBUNTU-CVE-2025-10728

## What is CVE-2025-10728?

CVE-2025-10728 is a critical denial of service vulnerability in Qt, published on 3 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When the module renders a Svg file that contains a <pattern> element, it might end up rendering it recursively leading to stack overflow DoS

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2025-10728?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qt6-qtsvg` | AlmaLinux:10 | All versions | 6.9.1-2.el10_1.2 |
| `qt6-qtsvg-devel` | AlmaLinux:10 | All versions | 6.9.1-2.el10_1.2 |
| `qt6-qtsvg-examples` | AlmaLinux:10 | All versions | 6.9.1-2.el10_1.2 |
| `qt6-qtsvg` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg-examples` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg-tests-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.9.1-2.el10_1.2 |
| `qt6-qtsvg` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg-examples` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg-tests-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-1.el10_0.2 |
| `qt6-qtsvg` | Rocky Linux:10 | All versions | 0:6.9.1-2.el10_1.2 |

## How do I fix CVE-2025-10728?

Apply the vendor's patch.

## Is CVE-2025-10728 being exploited?

There is no known exploitation of CVE-2025-10728 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10728 and fix it if it is affected.

What it is: CVE-2025-10728 is a critical denial of service vulnerability in Qt, published on 3 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10728 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-2025-10728/ (Markdown: https://insights.sbomify.com/CVE-2025-10728/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10728
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10728
- OSV: https://osv.dev/vulnerability/CVE-2025-10728

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10728/
Summaries are generated and may contain mistakes; the official description above is the record.