Skip to main content

Qt qt5compat EUVDEUVD-2026-104838

| CVE-2026-101201 MEDIUM
Integer Overflow or Wraparound (CWE-190)
2026-10-20 Qt GHSA-7cv7-2mxj-57c6
4.3
CVSS 4.0 · Vendor: Qt
View

Attack ChainAIDerived

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

  1. Access
    Craft malformed binary JSON header
  2. Delivery
    Deliver file to victim application
  3. Exploit
    Victim parses via fromBinaryData()
  4. Execution
    Out-of-bounds read / integer overflow triggered
  5. Impact
    Application crash or undefined behaviour

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target application use Qt's deprecated qt5compat module and specifically call QBinaryJson::fromBinaryData() to parse attacker-supplied binary JSON data - this is a legacy Qt5 compatibility feature, not a default code path in modern Qt6 applications. The attack vector is local (AV:L): the attacker must get the malformed binary file to the victim, and per UI:P the victim must open or process that file for the flaw to trigger. Limiting factors: no remote network reach, mandatory victim interaction, and dependence on an application actively consuming the obsolete binary JSON format - applications that do not use QBinaryJson are not exposed regardless of Qt version.

Impact

This is a genuinely low-to-moderate priority issue, not a top-tier threat despite affecting the widely-used Qt framework. The vendor CVSS 4.0 vector (score 4.3) tells a consistent, low-urgency story: AV:L means the attacker needs local delivery of a crafted file rather than remote network reach, UI:P means a victim must passively open or process that file, and the impact is confined to availability (VA:H) with no confidentiality or integrity loss (VC:N/VI:N) - consistent with an out-of-bounds read that produces a crash or undefined behaviour rather than code execution or data theft. The exploit-maturity metric E:U (unproven) aligns with the absence of any KEV listing or public POC in the provided data, so there is no evidence of active exploitation. No EPSS score was provided, so probabilistic exploitation likelihood cannot be factored in - this is a data gap, not a signal of low risk. No SSVC decision data was supplied either. The one point worth flagging: CWE-190 (Integer Overflow) combined with 'out-of-bounds read' could in principle leak adjacent memory (a confidentiality concern), yet the vendor scored VC:N; the description only characterizes the result as 'undefined behaviour,' so the availability-only impact is plausible but the possibility of limited information disclosure cannot be fully excluded from the description alone. Overall: a low-CVSS, low-real-risk DoS-class bug gated behind local file delivery and use of a deprecated Qt feature.

Exploit ScenarioDerived

An attacker crafts a binary JSON file with a malformed header and delivers it to a victim (e.g., as an email attachment or download) whose application uses Qt's legacy QBinaryJson::fromBinaryData() to parse it. When the victim opens the file, the malformed header triggers an integer-overflow-driven out-of-bounds read, causing undefined behaviour and most likely a crash of the host application. No public exploit identified at time of analysis, and exploitation requires local delivery plus victim interaction.

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

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

Alert me

AnalysisAIv1 – Oct 20, 2026

Out-of-bounds read in Qt's qt5compat module can cause undefined behavior and application crash when QBinaryJson::fromBinaryData() processes a malformed binary JSON header. Only applications linked against the deprecated qt5compat compatibility module and explicitly using that legacy parser are exposed; a local, unauthenticated attacker must get a crafted file to the victim and the victim must open or process it. No public exploit identified at time of analysis, and the issue is assessed as low-to-moderate priority with availability impact only.

RemediationAI

Patch available per vendor advisory; consult https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-101201 and the qt5compat code review changesets at https://codereview.qt-project.org/c/qt/qt5compat/+/758925 and https://codereview.qt-project.org/c/qt/qt5compat/+/759230, noting that an exact fixed release version is not specified in the supplied data. Until a fixed build is deployed, remove or avoid the deprecated qt5compat dependency and migrate binary JSON handling to maintained Qt JSON APIs where feasible; this breaks compatibility with legacy binary JSON and requires code changes. If migration is not possible, prevent QBinaryJson::fromBinaryData() from parsing untrusted files, restrict ingestion to trusted sources, or add strict header and size validation before invoking the legacy parser; these controls reduce exposure but do not fix the underlying out-of-bounds read and may reject valid legacy data.

Affected VersionsENISA

Qt 5.0.0 ≤6.8.8
Qt 6.9.0 ≤6.11.2

Affected Packages

euvd qt no fix

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

Qt's qt5compat module provides Qt5 compatibility APIs for Qt6 applications, including the legacy QBinaryJson parser. QBinaryJson::fromBinaryData() parses an obsolete binary JSON serialization format; a malformed header can cause incorrect length or size handling associated with CWE-190 integer overflow/wraparound, leading to insufficient bounds validation and an out-of-bounds read. The independent assessment uses CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, meaning local unauthenticated access, required user interaction, no confidentiality or integrity impact, and high availability impact through crash or undefined behavior. The CPE cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:* identifies Qt broadly but provides no version boundary, and exposure is limited to applications that use the deprecated qt5compat module and call this legacy parser rather than default Qt6 code paths.

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 4.3 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/R:U/RE:L/U:Amber
vuln.today AI 5.5 MEDIUM

Local crafted-file delivery (AV:L) with mandatory victim parsing (UI:R), no privileges needed (PR:N); out-of-bounds read yields a crash, so availability-only impact (A:H, C:N/I:N).

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

Primary rating from Vendor (Qt).

CVSS VectorVendor: Qt

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

DescriptionCVE.org

A malformed header in the binary file fed to QBinaryJson::fromBinaryData() can cause undefined behaviour because of out-of-bounds read.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Qt framework widely deployed; legacy qt5compat binary JSON parser rarely used
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor CIRCL VulDB

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.1%
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
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

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

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

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