CVE-2026-25627 | NanoMQ MQTT Broker up to 0.24.7 MQTT Packet out-of-bounds (GHSA-w4rh-v3h2-j29x)

VDB-354268 · CVE-2026-25627 · GHSA-W4RH-V3H2-J29X NANOMQ MQTT BROKER UP TO 0.24.7 MQTT PACKET OUT-OF-BOUNDS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.3 $0-$5k 1.42+ Summaryinfo 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. Detailsinfo 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. Productinfo Vendor NanoMQ Name MQTT Broker Version 0.24.0 0.24.1 0.24.2 0.24.3 0.24.4 0.24.5 0.24.6 0.24.7 License open-source CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.4 VulDB 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): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Out-of-bounds CWE: 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 Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: MQTT Broker 0.24.8 Patch: e80b30bad6d855593a68d18f2785bfaca6faf09e Timelineinfo 02/04/2026 CVE reserved 03/30/2026 +54 days VulDB entry created 03/31/2026 +0 days Advisory disclosed 03/31/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-w4rh-v3h2-j29x Status: Confirmed CVE: CVE-2026-25627 (🔒) GCVE (CVE): GCVE-0-2026-25627 GCVE (VulDB): GCVE-100-354268 Entryinfo Created: 03/31/2026 00:18 Changes: 03/31/2026 00:18 (68) Complete: 🔍 Cache ID: 99:1F5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸