# CVE-2025-14576: Possible QML code injection in VectorImage component > Attackers can inject arbitrary QML/JavaScript code via malicious SVG files in Qt Quick applications, potentially causing code execution or data leaks. - **Severity:** High 7.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 Apr 2026 - **Updated:** 29 Jul 2026 - **Also known as:** DEBIAN-CVE-2025-14576, GHSA-4hpm-v49g-rq7q, RHSA-2026:20567, RHSA-2026:24987, RHSA-2026:7620, RHSA-2026:7846, RLSA-2026:20567, UBUNTU-CVE-2025-14576 ## What is CVE-2025-14576? CVE-2025-14576 is a high-severity code injection vulnerability in Qt, published on 30 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Insufficient validation of node IDs in Qt SVG module allows arbitrary QML/JavaScript code injection when loading malicious SVG files through the VectorImage component in Qt Quick. While QML execution is typically more restricted than native code execution, this could still lead to denial of service, information disclosure, or other impacts depending on the application's privilege level and data access. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2025-14576? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qt6-qtdeclarative` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-devel-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-examples` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-examples-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-static` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative-tests-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:6.10.1-1.el10_2.1 | | `qt6-qtdeclarative` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-devel-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-examples` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-examples-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-static` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt6-qtdeclarative-tests-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:6.8.1-5.el10_0 | | `qt5` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-2.1.hum1 | | `qt5-filesystem` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-2.1.hum1 | | `qt5-rpm-macros` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-2.1.hum1 | | `qt5-srpm-macros` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-2.1.hum1 | | `qt6` | Red Hat:hummingbird:1 | All versions | 0:6.11.0-1.hum1 | | `qt6-filesystem` | Red Hat:hummingbird:1 | All versions | 0:6.11.0-1.hum1 | | `qt6-rpm-macros` | Red Hat:hummingbird:1 | All versions | 0:6.11.0-1.hum1 | | `qt6-srpm-macros` | Red Hat:hummingbird:1 | All versions | 0:6.11.0-1.hum1 | | `qt6-qtdeclarative` | Rocky Linux:10 | All versions | 0:6.10.1-1.el10_2.1 | Products: Qt Qtdeclarative. ## How do I fix CVE-2025-14576? Apply the vendor's patch. ## Is CVE-2025-14576 being exploited? There is no known exploitation of CVE-2025-14576 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-14576 and fix it if it is affected. What it is: CVE-2025-14576 is a high-severity code injection vulnerability in Qt, published on 30 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-14576 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-14576/ (Markdown: https://insights.sbomify.com/CVE-2025-14576/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14576 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14576 - OSV: https://osv.dev/vulnerability/CVE-2025-14576 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-14576/ Summaries are generated and may contain mistakes; the official description above is the record.