Skip to main content

Qt for MCUs EUVDEUVD-2026-92384

| CVE-2026-19395 MEDIUM
Reachable Assertion (CWE-617)
2026-10-05 Qt GHSA-4vr6-gg46-c2vh
6.6
CVSS 4.0 · Vendor: Qt
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver styled text with empty <img> attribute
  2. Exploit
    Parser passes empty value to non-empty check
  3. Execution
    Check fails and raises error
  4. Impact
    Default handler halts device

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V16 - Security Logging and Error Handling Reachable assertion handling
Exploitation Conditions

Exploitation requires that a Qt for MCUs application use a Text element configured to render styled/rich text (HTML-style markup) AND that the attacker be able to influence that text so it contains an <img> tag with an attribute whose value is empty. Limiting factors: the application must actually parse styled text (plain-text Text elements are unaffected), and exploitability hinges on whether that text is attacker-controllable and network-reachable - the AV:N rating assumes it is, but the description does not confirm the delivery path, so devices that render only trusted/static strings are not exposed. Impact is confined to a device halt (availability); no code execution, data disclosure, or integrity impact occurs.

Impact

This is an availability-only denial-of-service (device halt) issue, not a confidentiality or integrity flaw. The vendor CVSS:4.0 vector (AV:N/AC:L/PR:N/UI:N) describes an unauthenticated, low-complexity trigger with impact limited strictly to availability (VC:N/VI:N/VA:H), consistent with the CWE-617 reachable-assertion root cause: a styled-text <img> tag with an empty attribute value fails an internal non-empty check, and the default error handler halts the device. The E:U value in the vector indicates no proven/public exploit, and there is no EPSS score, no CISA KEV listing, and no POC provided in the input - so despite the 'network' attack vector, there is no evidence of real-world or automated exploitation. The practical risk is therefore moderate and conditional: it matters only where a Qt for MCUs application renders attacker-influenced styled text, and the single-value-only nature (device reset/halt rather than code execution or data exposure) plus the embedded, niche deployment footprint keep this below the priority of a typical remotely exploitable RCE. Note a labeling conflict: the input Tags include 'Information Disclosure,' which contradicts the CVSS impact metrics (VC:N, no confidentiality impact) - this appears to be a mislabeled tag and should not drive triage.

Exploit ScenarioDerived

An attacker supplies styled/rich text containing an <img> tag with an empty attribute value (e.g. an empty src) to a Qt for MCUs application that renders it in a Text element; the parser hits the failed non-empty check and the default error handler halts the embedded device. No public exploit code is identified at time of analysis, and the vector marks exploit maturity as unproven. Realistic exploitability depends on whether the device renders attacker-controllable text.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

Device halt - an availability-only denial of service - in Qt for MCUs is triggered when a Text element rendering styled (rich) text encounters an <img> tag with an attribute whose value is empty, causing an internal validation check to fail and the default error handler to abort execution. Per the CVSS vectors (PR:N/UI:N) the trigger is reachable without authentication or user interaction, but exposure is conditional: only applications that parse styled markup and allow attacker-influenced text into the Text element are affected, and plain-text Text elements are not. There is no code execution, data disclosure, or integrity impact, and no public exploit has been identified at time of analysis (CVSS E:U).

RemediationAI

No vendor-released patch identified at time of analysis: the only reference provided, Qt's list of known vulnerabilities in Qt products (https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-19395), documents the issue but names no fixed version, so no exact patched release can be cited; monitor Qt for MCUs release notes for a corrected build and upgrade to the first release that addresses CVE-2026-19395. Until then, the most direct mitigation is to stop attacker-influenced strings from reaching a styled-text Text element - sanitize or strip markup before assignment and specifically reject or rewrite any <img> tag whose attribute values are empty; the trade-off is extra parsing work on the device and loss of some HTML-style formatting. Where rich formatting is unnecessary, configure the Text element for plain text, which avoids the vulnerable parser path entirely at the cost of visual styling. Also tighten the channels that deliver external text to the device (network services, provisioning interfaces, remote content updates) so untrusted strings cannot be rendered, accepting reduced dynamic-content functionality in exchange. If the application can override Qt's default error handler, replacing halt-on-error behavior with logging and recovery would keep the device alive after a parser failure, though internal state may be left undefined. Finally, validate and escape content at the trust boundary and treat the Qt advisory page as the tracking source until a patched version is published.

Affected VersionsENISA

Qt for MCUs 2.12.0 <2.12.3

Affected Packages

euvd qt_for_mcus fix: 2.12.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The defect sits in the rich/styled-text parser behind the Qt for MCUs Text element - the embedded Qt variant that targets microcontroller-class devices with a compact rendering and layout stack. While walking markup, the parser forwards an <img> tag's attribute value into an internal check written to accept only non-empty values; an explicitly empty attribute therefore reaches an assertion-style failure that reports an error, and because the default error handler is designed to halt the device (sensible for a fatal internal inconsistency on a constrained MCU), execution stops instead of degrading gracefully. This is CWE-617 (Reachable Assertion), the class of defects in which untrusted input drives the program into an assertion that aborts execution; here the abort is the whole impact. The CPE record cpe:2.3:a:qt:qt_for_mcus:*:*:*:*:*:*:*:* carries a wildcard version field, so the feed does not narrow the affected release range. Attribution is to Qt, with the sole reference being Qt's list of known vulnerabilities in Qt products. One metadata tag labels the issue as information disclosure, but neither the description nor the assessed vector (C:N/I:N/A:H) supports any confidentiality or integrity effect - the only confirmed outcome is loss of availability.

Know when Qt gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Qt) PRIMARY 6.6 MEDIUM
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/E:U
vuln.today AI 7.5 HIGH

Low-complexity, unauthenticated reachable assertion halting the device yields A:H with C:N/I:N; AV:N follows the vendor assumption that styled text is attacker-reachable, though local delivery would warrant AV:L.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Red Hat 7.5 HIGH

Primary rating from Vendor (Qt).

CVSS VectorVendor: Qt

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 05, 2026 - 11:16 EUVD

DescriptionCVE.org

In Qt for MCUs, a Text element that displays styled text halts the device if an <img> tag in the text contains an attribute with an empty value. The text parser passes the empty value to an internal check that only accepts non-empty values. The check fails and reports an error, and the default error handler halts the device.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
embedded GUI framework for microcontrollers, niche industry-specific footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

33
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +33
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

More in Qt

View all
CVE-2020-12267 CRITICAL POC
9.8 Apr 27

setMarkdown in Qt before 5.14.2 has a use-after-free related to QTextMarkdownImporter::insertBlock. Rated critical sever

CVE-2023-37369 HIGH POC
7.5 Aug 20

In Qt before 5.15.15, 6.x before 6.2.9, and 6.3.x through 6.5.x before 6.5.2, there can be an application crash in QXmlS

CVE-2020-13962 HIGH POC
7.5 Jun 09

Qt 5.12.2 through 5.14.2, as used in unofficial builds of Mumble 1.3.0 and other products, mishandles OpenSSL's error qu

CVE-2020-0570 HIGH POC
7.3 Sep 14

Uncontrolled search path in the QT Library before 5.14.0, 5.12.7 and 5.9.10 may allow an authenticated user to potential

CVE-2023-51714 CRITICAL
9.8 Dec 24

An issue was discovered in the HTTP2 implementation in Qt before 5.15.17, 6.x before 6.2.11, 6.3.x through 6.5.x before

CVE-2024-36048 CRITICAL
9.8 May 18

QAbstractOAuth in Qt Network Authorization in Qt before 5.15.17, 6.x before 6.2.13, 6.3.x through 6.5.x before 6.5.6, an

CVE-2017-10904 CRITICAL
9.8 Dec 16

Qt for Android prior to 5.9.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors. Rated cr

CVE-2018-19873 CRITICAL
9.8 Dec 26

An issue was discovered in Qt before 5.11.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploita

CVE-2016-10040 MEDIUM POC
5.5 Mar 07

Stack-based buffer overflow in QXmlSimpleReader in Qt 4.8.5 allows remote attackers to cause a denial of service (applic

CVE-2026-95509 HIGH
8.8 Sep 29

Out-of-bounds read in Qt for MCUs occurs when an application passes a Latin-1-optimized string containing Latin-1 charac

CVE-2018-19870 HIGH
8.8 Dec 26

An issue was discovered in Qt before 5.11.3. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable,

CVE-2018-15518 HIGH
8.8 Dec 26

QXmlStream in Qt 5.x before 5.11.3 has a double-free or corruption during parsing of a specially crafted illegal XML doc

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy