NanoMQ MQTT Broker up to 0.24.7 MQTT Packet out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.76 |
Summary
A vulnerability described as problematic has been identified in NanoMQ MQTT Broker up to 0.24.7. This affects an unknown part of the component MQTT Packet Handler. Executing a manipulation can lead to out-of-bounds. This vulnerability appears as CVE-2026-25627. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in NanoMQ MQTT Broker up to 0.24.7. This vulnerability affects an unknown code block of the component MQTT Packet Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect availability. CVE summarizes:
NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to version 0.24.8, NanoMQ’s MQTT-over-WebSocket transport can be crashed by sending an MQTT packet with a deliberately large Remaining Length in the fixed header while providing a much shorter actual payload. The code path copies Remaining Length bytes without verifying that the current receive buffer contains that many bytes, resulting in an out-of-bounds read (ASAN reports OOB / crash). This is remotely triggerable over the WebSocket listener. This issue has been patched in version 0.24.8.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-25627 since 02/04/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 0.24.8 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e80b30bad6d855593a68d18f2785bfaca6faf09e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: MQTT Broker 0.24.8
Patch: e80b30bad6d855593a68d18f2785bfaca6faf09e
Timeline
02/04/2026 CVE reserved03/30/2026 VulDB entry created
03/31/2026 Advisory disclosed
03/31/2026 VulDB entry last update
Sources
Advisory: GHSA-w4rh-v3h2-j29xStatus: Confirmed
CVE: CVE-2026-25627 (🔒)
GCVE (CVE): GCVE-0-2026-25627
GCVE (VulDB): GCVE-100-354268
Entry
Created: 03/31/2026 00:18Changes: 03/31/2026 00:18 (68)
Complete: 🔍
Cache ID: 216:541:103
No comments yet. Languages: en.
Please log in to comment.