Security readout for executives and security teams
Plain-English summary
Qt applications using the Qt Quick Text component may freeze when processing an image tag containing inadequately validated dimensions. The issue primarily threatens application availability rather than data confidentiality or integrity. Risk is greatest when an application renders markup supplied by remote or untrusted sources.
Executive priority
Prioritize applications that render externally controlled markup, especially remotely reachable services or widely deployed clients. Schedule prompt remediation because exploitation requires no privileges or user interaction and can disrupt availability. Lower priority may be appropriate where Qt Quick Text is unused or all rendered markup is strongly trusted and constrained.
Technical view
CVE-2025-12385 is a resource-allocation flaw caused by missing width and height validation for <img> tags in Qt Quick Text. It affects Qt 5.0.0–6.5.10, 6.6.0–6.8.5, and 6.9.0–6.10.0 across the listed platforms and architectures. Crafted input can cause excessive allocation and make an application unresponsive.
Likely exposure
Exposure requires an affected Qt version, use of the Qt Quick Text component, and a path for attacker-controlled or insufficiently trusted markup to reach it. Internet-facing applications, messaging clients, content viewers, and other markup-rendering software may warrant priority review, but these application categories are not explicitly confirmed by the sources.
Exploitation context
The CVSS 4.0 assessment is 8.7 with network reachability, low complexity, no privileges, and no user interaction. Impact is limited to availability in the supplied vector. The CVE is not listed as KEV in the bundle, and no cited evidence establishes active exploitation or public weaponization.
Researcher notes
The weakness maps to CWE-1284 and CWE-770: quantity validation failure leading to unbounded resource allocation. The supplied sources identify two Qt code-review changes but do not explicitly name fixed release versions, backport status, exploit prevalence, or the exact allocation primitive. Confirm branch-specific remediation directly with Qt guidance.
Mitigation direction
- Upgrade to a vendor-supported Qt release outside the documented affected ranges.
- Confirm the selected release incorporates the referenced Qt declarative parser changes.
- Until updated, prevent untrusted markup from reaching Qt Quick Text components.
- Constrain or reject untrusted image dimensions before rendering.
- Review current Qt vendor guidance for supported branches and backports.
Validation and detection
- Inventory deployed Qt versions and identify builds within each affected interval.
- Locate Qt Quick Text components that accept dynamic or externally sourced markup.
- Trace whether remote or untrusted <img> attributes can reach those components.
- Verify updated binaries use a version outside the affected ranges.
- Perform controlled availability regression testing using safe boundary-value image dimensions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-1284: 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 lookupCWE-770: 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 lookupCVE-2025-12385 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——TQtCVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://codereview.qt-project.org/c/qt/qtdeclarative/+/687239CVE reference, TQtC
- https://codereview.qt-project.org/c/qt/qtdeclarative/+/687766CVE reference, TQtC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.