Security readout for executives and security teams
Plain-English summary
A malformed data URL can crash affected Qt applications built with assertions enabled. The issue creates a denial-of-service risk when an application processes attacker-influenced content through affected Qt functionality. The supplied evidence describes an abort, not code execution or data theft.
Executive priority
Prioritize internet-facing or user-content-processing applications that combine affected Qt versions with assertions enabled. Remediate promptly where crashes could interrupt critical services. Lower urgency may be appropriate only after confirming malformed data URLs cannot reach affected processing paths.
Technical view
The private QtCore function qDecodeDataUrl(), used by QTextDocument, QNetworkReply, and potentially application code, can assert on malformed data URL parameters lacking values. Affected assertion-enabled builds may abort. Reported affected releases are through 5.15.18, 6.5.8, 6.8.3, and 6.9.0 across their respective branches.
Likely exposure
Exposure is most likely where assertion-enabled Qt applications process untrusted or attacker-influenced data URLs through QTextDocument, QNetworkReply, or direct use of related functionality. Production builds without assertions may not experience the described abort; the supplied sources do not establish their behavior conclusively.
Exploitation context
The malformed input may arrive remotely, but the CVSS vector indicates user interaction is required. The source bundle does not report active exploitation, and the CVE is not listed as KEV in the supplied data. No exploit prevalence or affected deployment count is established.
Researcher notes
CWE-20 applies because malformed input is not handled safely before an assertion. The supplied description supports denial of service through process abort only. Although the CVSS vector includes integrity impacts, the bundle provides no technical explanation for data modification, so that consequence should not be asserted without additional evidence.
Mitigation direction
- Upgrade Qt 5.15 deployments to 5.15.19 or later within that supported branch.
- Upgrade Qt 6.5, 6.8, and 6.9 deployments to 6.5.9, 6.8.4, and 6.9.1 respectively.
- Restrict or reject untrusted data URLs until affected Qt components are upgraded.
- Check Qt vendor guidance for branch-specific backports and supported remediation options.
Validation and detection
- Inventory Qt versions and determine whether deployed binaries were built with assertions enabled.
- Identify paths where QTextDocument, QNetworkReply, or application code processes untrusted data URLs.
- Confirm deployed versions meet the fixed release for their respective Qt branch.
- Use controlled regression tests with malformed inputs; avoid testing against production systems.
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-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 lookupCVE-2025-5455 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.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/R:U/RE:M/U:Clear
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:A/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/R:U/RE:M/U:Clear——TQtCVulnerability scoring details
Base CVSS 4.0 score
8.4HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/R:U/RE:M/U:Clear
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/qtbase/+/642006CVE 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 Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.