CVE-2025-14576
Qt SVG Module QML/JavaScript Code Injection via VectorImage
Publication date: 2026-04-30
Last updated on: 2026-05-05
Assigner: TQtC
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qt | qtdeclarative | From 6.10.0 (inc) to 6.10.1 (exc) |
| qt | qtdeclarative | From 6.8.0 (inc) to 6.8.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves insufficient validation of node IDs in the Qt SVG module. It allows an attacker to inject arbitrary QML or JavaScript code when a malicious SVG file is loaded through the VectorImage component in Qt Quick.
Although QML execution is generally more restricted than native code execution, this flaw can still be exploited to cause denial of service, disclose information, or produce other impacts depending on the application's privilege level and data access.
How can this vulnerability impact me? :
The vulnerability can lead to several impacts including denial of service, where the application or system may become unavailable or unstable.
It can also cause information disclosure, potentially exposing sensitive data handled by the affected application.
Other impacts depend on the privilege level and data access of the application, meaning that if the application has high privileges, the attacker could perform more severe actions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.