CVE-2025-23050VulnerabilityPublished 31 Oct 2025

CVE-2025-23050: Qt · Out-of-bounds Read

Affects QtSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low · fixed in 6.8.2 : update Qt when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.8.2, 6.5.9, 5.15.19

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.qtproject/qt to 6.8.2, 6.5.9 or 5.15.19.

Affected software

Product	Affected	Fixed in
Mavenorg.qtproject/qt`pkg:maven/org.qtproject/qt`Other threats	Affected <5.15.19 <6.5.9 <6.8.2	Fixed in 5.15.19 6.5.9 6.8.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-23050, European organizations should: 1) Immediately upgrade Qt to versions 5.15.19, 6.5.9, or 6.8.2 or later, where the vulnerability is fixed. 2) Audit all applications and embedded devices using Qt for BLE communications to identify vulnerable versions. 3) Implement strict input validation and sanitization of Bluetooth ATT commands at the application or firmware level to prevent malformed packets from triggering the flaw. 4) Employ network segmentation and Bluetooth access controls to limit exposure to untrusted devices, reducing the risk of malicious ATT command injection. 5) Monitor device logs and application behavior for signs of crashes or abnormal Bluetooth activity that could indicate exploitation attempts. 6) Coordinate with device manufacturers and software vendors to ensure timely patch deployment and firmware updates. 7) Incorporate vulnerability scanning and patch management processes specifically targeting embedded and IoT devices using Qt. These targeted actions go beyond generic advice by focusing on the Bluetooth ATT protocol handling and the specific Qt versions affected.

Description

QLowEnergyController in Qt before 6.8.2 mishandles malformed Bluetooth ATT commands, leading to an out-of-bounds read (or division by zero). This is fixed in 5.15.19, 6.5.9, and 6.8.2.

Impact

For European organizations, the primary impact of CVE-2025-23050 is the potential for denial of service in Bluetooth-enabled applications or devices using vulnerable Qt versions. This could disrupt critical operations in sectors relying on BLE communications, such as manufacturing automation, healthcare devices, smart building systems, and consumer electronics. While the vulnerability does not allow data leakage or unauthorized control, service interruptions could affect operational continuity and user experience. In industrial environments where BLE is used for sensor data collection or device management, repeated crashes could lead to downtime or require manual intervention. The low CVSS score indicates limited risk of widespread exploitation, but organizations with large deployments of embedded Qt-based systems should consider the cumulative impact. Additionally, the vulnerability could be leveraged as part of multi-stage attacks aiming to degrade system availability. European companies developing or deploying Qt-based BLE applications must assess their exposure and patch vulnerable components to maintain reliability and compliance with operational standards.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2025, 02:10 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats