CVE-2026-22040

NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash

Published Mar 4, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability is a use‑after‑free condition (CWE‑416) in NanoMQ 0.24.6. By sending a crafted traffic pattern that mixes high‑frequency publishes with rapid reconnects under the same ClientID and induces massive subscribe/unsubscribe churn, an attacker can trigger a heap‑memory corruption in the broker process. This corruption leads to the broker aborting with SIGABRT, effectively terminating the service and causing a denial of service for all clients.

Affected Systems

The weakness exists only in the NanoMQ MQTT Broker from the nanomq project, specifically version 0.24.6. No fixed version is currently available, so all deployments running this version are vulnerable. Until a patched release is issued, users should avoid running the affected edition.

Risk and Exploitability

The CVSS base score is 5.3, reflecting a moderate impact. EPSS is under 1 %, indicating a very low likelihood of exploitation in the wild at present. The vulnerability is not in the CISA KEV catalog. An attacker requires the ability to place MQTT traffic on the broker, so the path is remote but limited to clients with network reach to the broker. The lack of a publicly released fix means the priority for addressing the issue is to implement mitigation controls rather than rely on patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Limit publish and reconnect rates for every client, especially those that reuse the same ClientID, to prevent the trigger pattern.
  • Enforce unique ClientID usage and disallow concurrent reuse of the same identifier.
  • Set up monitoring of broker logs for SIGABRT crashes and configure alerts for rapid restart events.
  • Once a patched version of NanoMQ is released, upgrade the broker immediately.

Generated by OpenCVE AI on April 17, 2026 at 13:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Emqx
Emqx nanomq
CPEs cpe:2.3:a:emqx:nanomq:*:*:*:*:*:*:*:*
Vendors & Products Emqx
Emqx nanomq
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Nanomq
Nanomq nanomq
Vendors & Products Nanomq
Nanomq nanomq
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

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 5, 2026, 3:42 PM
Reserved
Jan 5, 2026, 10:30 PM
Status
Analyzed
Published
Mar 4, 2026, 10:16 PM
Modified
Jun 17, 2026, 10:19 AM