# CVE-2026-32134: NanoMQ NULL pointer dereference in tcptran_pipe_peer

Source: https://junglewise.ai/threats/cve-2026-32134-nanomq-null-pointer-dereference-in-tcptran-pipe-peer  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-19. Updated: 2026-05-19  
License: CC BY 4.0 with a link back

CVE-2026-32134 · Severity: medium · CVSS 5.9 · Published 2026-05-19

NanoMQ is a messaging platform used to connect and manage data from smart devices. A vulnerability in how it handles high volumes of reconnecting devices can cause the service to crash. This allows a remote attacker to disrupt operations and cause a denial-of-service without needing any login credentials.

Technologies: [EMQ NanoMQ](https://junglewise.ai/threats/technologies/nanomq). Vendors: [EMQ](https://junglewise.ai/threats/vendors/emq).

## Quick answers

**Is CVE-2026-32134 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-32134 being exploited in the wild.

**How severe is CVE-2026-32134?** Medium severity, with a CVSS score of 5.9, published 19 May 2026.

**Which products and versions are affected?** EMQ NanoMQ <= 0.24.10.

**Is there a fix for CVE-2026-32134?** A patch was published on 2026-03-12: Version 0.24.11 released to address the issue. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-32134 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-32134?** Check whether you run EMQ NanoMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A NULL pointer dereference exists in NanoMQ versions 0.24.10 and below within the tcptran_pipe_peer() function. The vulnerability is triggered during MQTT session resumption for clients with clean_start=0 when the broker is under high-concurrency reconnect pressure. Specifically, a race condition allows the session metadata pointer (cpipe->subinfol) to be freed and set to NULL before the transport callback attempts to iterate through it. An unauthenticated remote attacker can exploit this by sending a specific reconnect-collision payload, leading to a process crash. This issue has been resolved in version 0.24.11.

## Affected products

- NanoMQ NanoMQ <= 0.24.10

## Timeline

- 2026-03-12: patched: Version 0.24.11 released to address the issue.
- 2026-05-19: disclosed: Public advisory and CVE published.

## References

- [https://github.com/nanomq/NanoNNG/commit/522ec62e29e60d1122f2aedaa6e702dcf089f7bb](https://github.com/nanomq/NanoNNG/commit/522ec62e29e60d1122f2aedaa6e702dcf089f7bb)
- [https://github.com/nanomq/nanomq/issues/2241](https://github.com/nanomq/nanomq/issues/2241)
- [https://github.com/nanomq/nanomq/releases/tag/0.24.11](https://github.com/nanomq/nanomq/releases/tag/0.24.11)
- [https://github.com/nanomq/nanomq/security/advisories/GHSA-q36f-83mh-pcv2](https://github.com/nanomq/nanomq/security/advisories/GHSA-q36f-83mh-pcv2)

## Related threats

- [NanoMQ NULL pointer dereference in REST API properties_parse](https://junglewise.ai/threats/cve-2026-47276-nanomq-null-pointer-dereference-in-rest-api-properties-parse)
- [NanoMQ NULL pointer dereference in nni_mqttv5_msg_decode_connect](https://junglewise.ai/threats/cve-2026-47275-nanomq-null-pointer-dereference-in-nni-mqttv5-msg-decode-connect)
- [NanoMQ MQTT v5 SUBSCRIBE out-of-bounds read and semantic flaw](https://junglewise.ai/threats/cve-2026-35217-nanomq-mqtt-v5-subscribe-out-of-bounds-read-and-semantic-flaw)
- [EMQ NanoMQ denial of service via memory leak in nni_qos_db_set](https://junglewise.ai/threats/cve-2026-36590-emq-nanomq-denial-of-service-via-memory-leak-in-nni-qos-db-set)
- [NanoMQ type confusion in QUIC dialer close path](https://junglewise.ai/threats/cve-2026-44640-nanomq-type-confusion-in-quic-dialer-close-path)