CVE-2026-94370
Deferred Deferred - Pending Action

Heap Memory Corruption in Qt for MCUs via String Handling

Publication date: 2026-10-14

Last updated on: 2026-10-14

Assigner: TQtC

Description
A defect in the Qt for MCUs core string handling causes heap memory corruption. When an application passes text into Qt Quick Ultralite using the public Qul::String interface type, and that text is held in a std::string, the conversion to the internal string type copies the pointer without taking ownership of it. Two objects then release the same memory, producing a double free, an invalid free, or a use-after-free.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-14
Last Modified
2026-10-14
Generated
2026-10-19
AI Q&A
2026-10-14
EPSS Evaluated
2026-10-18
NVD
CVE-2026-94370
EUVD
EUVD-2026-100839

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
qt Qt_for_MCUs 2.12.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
CWE-415 The product calls free() twice on the same memory address.
CWE-590 The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
CWE-665 The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a heap memory corruption issue in Qt for MCUs caused by improper string handling. When text is passed using the Qul::String interface type and stored in a std::string, the conversion to the internal string type copies the pointer without transferring ownership. This leads to two objects releasing the same memory, causing double free, invalid free, or use-after-free scenarios.

Detection Guidance

This vulnerability involves heap memory corruption in Qt for MCUs due to improper string handling. Detection requires checking for applications using Qt Quick Ultralite with std::string inputs passed via Qul::String. Inspect memory dumps for double free, invalid free, or use-after-free errors in Qt for MCUs applications. No specific commands are provided in the context.

Impact Analysis

The vulnerability can lead to crashes, data corruption, or arbitrary code execution. Attackers could exploit it to gain control over the affected application, potentially leading to system compromise depending on the application's privileges and context.

Compliance Impact

This vulnerability could lead to memory corruption issues such as double free, invalid free, or use-after-free. Such flaws may cause application crashes or unpredictable behavior, potentially resulting in unauthorized data access or modification. This could violate GDPR's integrity and confidentiality principles or HIPAA's security requirements for protected health information.

Mitigation Strategies

Update Qt for MCUs to the latest version to address the heap memory corruption issue in string handling. Review applications using Qul::String to ensure proper memory ownership and avoid double free or use-after-free conditions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-94370. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart