Broker crash via unreleased QoS message references
Published Jul 15, 2026 · Updated Jul 15, 2026
Resource exhaustion in EMQ NanoMQ 0.24.9 allows remote attackers to crash the broker through repeated QoS MQTT PUBLISH messages. The nni_qos_db_set function returns when its database pointer is NULL without releasing the cloned message reference, so each qualifying message leaks memory. The path requires sqlite.enable=true in a build without SQLite support; sustained unauthenticated traffic exhausts memory until the broker crashes.
Summary
What happened
Resource exhaustion in EMQ NanoMQ 0.24.9 allows remote attackers to crash the broker through repeated QoS MQTT PUBLISH messages. The nni_qos_db_set function returns when its database pointer is NULL without releasing the cloned message reference, so each qualifying message leaks memory. The path requires sqlite.enable=true in a build without SQLite support; sustained unauthenticated traffic exhausts memory until the broker crashes.
The record
- CVE
- CVE-2026-36590
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-772, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- 249exploit_leak.pyproof 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