Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 18 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Emqx
Emqx nanomq |
|
| CPEs | cpe:2.3:a:emqx:nanomq:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Emqx
Emqx nanomq |
Thu, 05 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 05 Mar 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nanomq
Nanomq nanomq |
|
| Vendors & Products |
Nanomq
Nanomq nanomq |
Wed, 04 Mar 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In version 0.24.6, by generating a combined traffic pattern of high-frequency publishes and rapid reconnect/kick-out using the same ClientID and massive subscribe/unsubscribe jitter, it is possible to reliably trigger heap memory corruption in the Broker process, causing it to exit immediately with SIGABRT due to free(): invalid pointer. As of time of publication, no known patched versions are available. | |
| Title | NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-05T15:42:26.352Z
Reserved: 2026-01-05T22:30:38.719Z
Link: CVE-2026-22040
Updated: 2026-03-05T15:29:17.896Z
Status : Analyzed
Published: 2026-03-04T22:16:17.300
Modified: 2026-03-18T16:09:07.133
Link: CVE-2026-22040
No data.
OpenCVE Enrichment
Updated: 2026-04-17T13:15:19Z