CVE-2026-47276
Received Received - Intake

NULL Pointer Dereference in NanoMQ Broker

Publication date: 2026-07-20

Last updated on: 2026-07-20

Assigner: GitHub, Inc.

Description
In nanomq versions 0.24.11 and earlier, a NULL pointer dereference in `properties_parse()` allows an authenticated attacker to crash the NanoMQ broker by sending a POST request to `/api/v4/mqtt/publish` with `user_properties` as a JSON array instead of a JSON object. The crash occurs because `strlen()` is called on a NULL `item->string` pointer when iterating over array elements. An authenticated attacker can exploit this to crash the NanoMQ broker process. This is patched in version 0.24.14.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-20
Last Modified
2026-07-20
Generated
2026-07-21
AI Q&A
2026-07-20
EPSS Evaluated
N/A
NVD
CVE-2026-47276
EUVD
EUVD-2026-46025

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
nanomq nanomq to 0.24.11 (inc)
nanomq nanomq 0.24.14

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a NULL pointer dereference in the NanoMQ broker's REST API. An authenticated attacker can crash the broker by sending a POST request to /api/v4/mqtt/publish with user_properties as a JSON array instead of a JSON object. The crash happens because the code calls strlen() on a NULL pointer when processing array elements.

Detection Guidance

Monitor NanoMQ broker logs for crashes or segmentation faults. Check for POST requests to /api/v4/mqtt/publish with user_properties as a JSON array. Use tools like tcpdump or Wireshark to inspect network traffic for malformed MQTT REST API requests targeting the vulnerable endpoint.

Impact Analysis

This vulnerability can cause a denial-of-service (DoS) condition by crashing the NanoMQ broker. When exploited, it disconnects all connected MQTT clients and makes the broker unavailable until restarted. The attacker needs valid credentials to exploit it.

Compliance Impact

This vulnerability primarily impacts availability by crashing the NanoMQ broker, which could disrupt services handling sensitive data. For GDPR, this may affect data processing continuity and availability of personal data. For HIPAA, it could interrupt systems managing protected health information, potentially violating access and integrity requirements.

Mitigation Strategies

Upgrade NanoMQ to version 0.24.14 or later. Restrict access to the REST API endpoint /api/v4/mqtt/publish by changing default credentials from admin:public to strong passwords. Implement network-level controls to block unauthorized access to the vulnerable API.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47276. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart