CVE-2025-3512: Buffer overflow in QTextMarkdownImporter
There is a Heap-based Buffer Overflow vulnerability in QTextMarkdownImporter. This requires an incorrectly formatted markdown file to be passed to QTextMarkdownImporter to trigger the overflow.
This issue affects Qt from 6.8.0 to 6.8.4. Versions up to 6.6.0 are known to be unaffected, and the fix is in 6.8.4 and later.
Security readout for executives and security teams
Plain-English summary
A malformed Markdown file can cause affected Qt applications to overwrite heap memory while importing the file. The supplied CVSS assessment indicates limited availability impact, requiring local file handling and user participation, with no stated confidentiality or integrity impact.
Executive priority
Prioritize normal-cycle remediation for products that import user-supplied Markdown using Qt 6.8.x. Accelerate updates where files originate from untrusted parties or processing occurs in important services. Current evidence does not justify emergency incident response by itself.
Technical view
CVE-2025-3512 is a CWE-122 heap-based buffer overflow in QTextMarkdownImporter. Triggering requires an incorrectly formatted Markdown file. The record identifies Qt 6.8.0 through 6.8.4, while also stating the fix is in 6.8.4 and later; this boundary is ambiguous.
Likely exposure
Exposure is most likely in applications using affected Qt 6.8 releases that pass untrusted or malformed Markdown into QTextMarkdownImporter. Systems not using this importer, and versions through 6.6.0, are reported unaffected.
Exploitation context
The CVSS vector describes local access, low complexity, no privileges, and passive user interaction. The supplied sources do not establish active exploitation, public weaponization, or inclusion in CISA KEV. The documented consequence is low availability impact.
Researcher notes
The record supports a heap overwrite and availability impact but does not document code execution, disclosure, or integrity loss. Review the referenced Qt change for root-cause and backport confirmation. Treat 6.8.4 cautiously until Qt's contradictory affected/fixed wording is resolved.
Mitigation direction
Upgrade to Qt 6.8.4 or later, consistent with the stated fixed-version guidance.
Confirm the precise fixed build with Qt because the supplied affected-version boundary is internally ambiguous.
Restrict untrusted Markdown from reaching QTextMarkdownImporter until affected deployments are updated.
Follow vendor guidance for supported backports if upgrading the Qt runtime is impractical.
Validation and detection
Inventory applications and embedded components using Qt 6.8.x.
Determine whether each application invokes QTextMarkdownImporter on externally supplied Markdown.
Verify the deployed Qt build includes the referenced Qt correction or an official backport.
Test importer failure handling with safe malformed-file regression cases in an isolated environment.
Confirm applications using Qt 6.6.0 or earlier match the reported unaffected range.
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-122: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.