CVE-2026-32696 | NanoMQ MQTT Broker up to 0.24.6 set_data null pointer dereference (GHSA-77f4-wvq8-mp3p)

VDB-354270 · CVE-2026-32696 · GHSA-77F4-WVQ8-MP3P NANOMQ MQTT BROKER UP TO 0.24.6 SET_DATA NULL POINTER DEREFERENCE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 3.0 $0-$5k 1.89+ Summaryinfo A vulnerability classified as problematic was found in NanoMQ MQTT Broker up to 0.24.6. This issue affects the function set_data. The manipulation results in null pointer dereference. This vulnerability is known as CVE-2026-32696. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as problematic, was found in NanoMQ MQTT Broker up to 0.24.6. Affected is the function set_data. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes: NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In NanoMQ version 0.24.6, after enabling auth.http_auth (HTTP authentication), when a client connects to the broker using MQTT CONNECT without providing username/password, and the configuration params uses the placeholders %u / %P (e.g., username="%u", password="%P"), the HTTP request construction phase enters auth_http.c:set_data(). This results in calling strlen() on a NULL pointer, causing a SIGSEGV crash. This crash can be triggered remotely, resulting in a denial of service. This issue has been patched in version 0.24.7. The advisory is available at github.com. This vulnerability is traded as CVE-2026-32696 since 03/13/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. Upgrading to version 0.24.7 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch c20aa27e5290bb480a5315099952480d35f37a8b 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 License open-source CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 3.1 VulDB Meta Temp Score: 3.0 VulDB Base Score: 3.1 VulDB Temp Score: 3.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 3.1 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: Null pointer dereference CWE: CWE-476 / CWE-404 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.7 Patch: c20aa27e5290bb480a5315099952480d35f37a8b Timelineinfo 03/13/2026 CVE reserved 03/30/2026 +17 days VulDB entry created 03/31/2026 +0 days Advisory disclosed 03/31/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-77f4-wvq8-mp3p Status: Confirmed CVE: CVE-2026-32696 (🔒) GCVE (CVE): GCVE-0-2026-32696 GCVE (VulDB): GCVE-100-354270 Entryinfo Created: 03/31/2026 00:18 Changes: 03/31/2026 00:18 (68) Complete: 🔍 Cache ID: 99:B0B:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸