Heap overwrite via undersized delivery vector
Published Dec 15, 2025 · Updated Dec 15, 2025
Heap buffer overflow in NanoMQ before 0.24.4 allows remote authenticated users to corrupt broker memory via crafted PUBLISH traffic. The foreach_client function grows the existing msg_infos vector to only the new context count, then appends entries beyond that allocation. An authenticated MQTT client must reach a routing state where shared and ordinary subscriptions both match; the overwrite corrupts broker memory and terminates instrumented builds.
Summary
What happened
Heap buffer overflow in NanoMQ before 0.24.4 allows remote authenticated users to corrupt broker memory via crafted PUBLISH traffic. The foreach_client function grows the existing msg_infos vector to only the new context count, then appends entries beyond that allocation. An authenticated MQTT client must reach a routing state where shared and ordinary subscriptions both match; the overwrite corrupts broker memory and terminates instrumented builds.
The record
- CVE
- CVE-2025-59947
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- EMQ Technologies
- Product
- NanoMQ
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 2025Record 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.4
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
No public exploit references are available in this record.
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