CVE-2025-14576: Possible QML code injection in VectorImage component
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.
Security readout for executives and security teams
Plain-English summary
A malicious SVG can inject QML/JavaScript into Qt Quick applications that load SVGs through VectorImage. Impact depends on the application’s privileges and data access, but the source notes possible denial of service, information disclosure, and other impacts. Exposure is most urgent where users or external systems can provide SVG files.
Executive priority
Treat as a high-priority patching and exposure review item for desktop or embedded products that process SVG files. It is not currently supported by the supplied sources as actively exploited, but the potential data and availability impact is material.
Technical view
Qt SVG insufficiently validates node IDs before VectorImage handling in Qt Quick, enabling QML/JavaScript injection from malicious SVG content. CVSS is 7.8: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact. The bundle lists Qt/qtdeclarative 6.8.0 and 6.10.0 as affected.
Likely exposure
Organizations are likely exposed if they ship Qt Quick applications using VectorImage and allow SVGs from users, partners, downloads, email, or other untrusted sources. Server-only systems without Qt Quick SVG rendering are less likely exposed based on the provided evidence.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires a malicious SVG to be loaded through the vulnerable VectorImage path, with user interaction indicated by the CVSS vector.
Researcher notes
Key unknowns are exact fixed version boundaries and application-specific sandboxing. The provided evidence supports QML/JavaScript injection through malicious SVG node IDs in VectorImage, not native code execution. Validation should focus on the vulnerable rendering path and trusted versus untrusted SVG sources.
Mitigation direction
Apply the Qt qtdeclarative patch or vendor-provided fixed packages.
Review Red Hat advisories if using affected Red Hat-distributed Qt packages.
Avoid loading untrusted SVG files through VectorImage until fixed.
Add file-source controls for user-supplied SVG content in affected applications.
Monitor Qt and OS vendor guidance for corrected package versions.
Validation and detection
Inventory applications using Qt Quick VectorImage with SVG input.
Confirm whether Qt/qtdeclarative 6.8.0 or 6.10.0 is present.
Verify the Qt patch or relevant Red Hat advisory update is installed.
Check whether SVG input can originate from untrusted users or external systems.
Document non-exposure where VectorImage or SVG loading is absent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.