Authenticated broker crash via malformed user properties
Published Jul 20, 2026 · Updated Jul 20, 2026
NULL pointer dereference in NanoMQ 0.24.11 and earlier allows remote authenticated users to crash the broker via its REST publish API. The properties_parse function treats user_properties arrays as objects and calls strlen on a null item key while iterating over array elements. Valid REST API credentials and network access to the HTTP service are required; one request terminates the broker and disconnects all MQTT clients.
Summary
What happened
NULL pointer dereference in NanoMQ 0.24.11 and earlier allows remote authenticated users to crash the broker via its REST publish API. The properties_parse function treats user_properties arrays as objects and calls strlen on a null item key while iterating over array elements. Valid REST API credentials and network access to the HTTP service are required; one request terminates the broker and disconnects all MQTT clients.
The record
- CVE
- CVE-2026-47276
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- EMQ Technologies
- Product
- NanoMQ
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 0.24.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated REST publish crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo