nanomq NanoMQ MQTT Broker up to 0.24.13 prov_data type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in nanomq NanoMQ MQTT Broker up to 0.24.13. The affected element is an unknown function. Executing a manipulation of the argument prov_data can lead to type confusion. The identification of this vulnerability is CVE-2026-44640. The attack can only be executed locally. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in nanomq NanoMQ MQTT Broker up to 0.24.13 and classified as problematic. This vulnerability affects an unknown part. The manipulation of the argument prov_data with an unknown input leads to a type confusion vulnerability. The CWE definition for the vulnerability is CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to 0.24.14, aio->prov_data is stored as nni_quic_conn* during dialing, but read as ex_quic_conn* during dialer close. This type confusion causes invalid object interpretation and leads to close-path hang/crash behavior. This vulnerability is fixed in 0.24.14.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-44640 since 05/07/2026. The exploitation appears to be difficult. The attack needs to be approached locally. There are known technical details, but no exploit is available.
Upgrading to version 0.24.14 eliminates this vulnerability. The upgrade is hosted for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-33428). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Type confusionCWE: CWE-843
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: NanoMQ MQTT Broker 0.24.14
Timeline
05/07/2026 CVE reserved05/30/2026 Advisory disclosed
05/30/2026 VulDB entry created
05/30/2026 VulDB entry last update
Sources
Advisory: GHSA-9fgw-v323-jmjjStatus: Confirmed
CVE: CVE-2026-44640 (🔒)
GCVE (CVE): GCVE-0-2026-44640
GCVE (VulDB): GCVE-100-367384
EUVD: 🔒
Entry
Created: 05/30/2026 07:33Updated: 05/30/2026 08:28
Changes: 05/30/2026 07:33 (65), 05/30/2026 08:28 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.