LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious SVG opened by an affected Qt application can inject QML or JavaScript through the VectorImage component. Successful exploitation requires user interaction but could expose information, alter application behavior, or crash the application, depending on its permissions and accessible data.

Executive priority

Prioritize affected applications that accept external SVG files or access sensitive data. Treat internet-facing upload and document workflows as urgent. Other deployments should be inventoried promptly, then patched through supported vendor channels. No evidence supplied supports emergency incident response solely for active exploitation.

Technical view

Qt SVG insufficiently validates SVG node IDs before VectorImage processes them, permitting QML/JavaScript injection. The supplied record identifies Qt 6.8.0 and 6.10.0, package qtdeclarative, and otherwise marks versions unaffected. CVSS 3.1 is 7.8 with local access and user interaction.

Likely exposure

Exposure is most likely where applications use affected Qt versions, invoke VectorImage, and accept attacker-influenced SVG files. Risk increases when the application handles sensitive information or runs with elevated access. The supplied evidence does not establish exposure for other Qt versions or components.

Exploitation context

The CVSS vector indicates a local attack requiring user interaction, such as loading a malicious SVG. QML execution is generally more restricted than native code, but impact remains application-dependent. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.

Researcher notes

The weakness maps to CWE-20 and CWE-94. Impact depends on the QML execution environment, application privileges, and reachable data. A Qt code-review patch exists, but the supplied bundle does not state fixed release numbers. Assessment should preserve the distinction between QML injection and unrestricted native-code execution.

Mitigation direction

  • Inventory applications containing qtdeclarative 6.8.0 or 6.10.0 and determine whether they use VectorImage.
  • Apply applicable Qt or distributor security updates after compatibility testing; the bundle does not identify fixed versions.
  • Until updated, prevent affected applications from loading untrusted or externally supplied SVG files.
  • Review the linked Qt patch and Red Hat advisories for platform-specific remediation guidance.

Validation and detection

  • Confirm installed or bundled qtdeclarative versions using software inventory and build records.
  • Search application code and dependencies for use of the Qt Quick VectorImage component.
  • Map every SVG input path and identify whether users, downloads, messages, or external systems can influence it.
  • After updating, verify deployed package versions against the applicable vendor advisory.
  • Run regression tests confirming trusted SVG rendering still works without exposing untrusted inputs.
Prepared
Confidence
high
Sources
5

Public sources used

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.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-14576 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9redhat-SADP
7.4CVSS 4.0HighCVSS: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——TQtC

Vulnerability scoring details

Base CVSS 4.0 score

7.4High
CVSS 4.0 vector shape for CVE-2025-14576Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPqt: Qt SVG: Arbitrary QML/JavaScript code injection via malicious SVG file
other:Red Hat severity ratingcvssV3_1
  • 2026-04-30T13:01:32.429Z: Reported to Red Hat.
  • 2026-04-30T12:39:40.067Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
QtQtqtdeclarative, 6.8.0, 6.10.0unaffected
Weakness

CWE details

CWE-20CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.