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.