NanoMQ up to 0.24.10 Peer Call tcptran_pipe_peer null pointer dereference

Summaryinfo

A vulnerability categorized as problematic has been discovered in NanoMQ up to 0.24.10. This vulnerability affects the function tcptran_pipe_peer of the component Peer Call Handler. Executing a manipulation can lead to null pointer dereference. This vulnerability appears as CVE-2026-32134. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in NanoMQ up to 0.24.10. This vulnerability affects the function tcptran_pipe_peer of the component Peer Call Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In versions 0.24.10 and below, when NanoMQ handles high-concurrency reconnect traffic using a reconnect-collision payload, the broker can crash due to a NULL pointer dereference during MQTT session resumption for clean_start=0 clients. The transport's p_peer callback (tcptran_pipe_peer()) iterates cpipe->subinfol while copying session metadata from the cached old pipe to the new reconnecting pipe, without checking whether the pointer is NULL. Under a reconnect race, cpipe->subinfol can be freed and set to NULL before session restore invokes this function, resulting in a remote unauthenticated Denial-of-Service (process crash) condition. This issue has been fixed in version 0.24.11.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-32134 since 03/10/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.

Upgrading to version 0.24.11 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 522ec62e29e60d1122f2aedaa6e702dcf089f7bb is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• NanoMQ

Version

• 0.24.0
• 0.24.1
• 0.24.2
• 0.24.3
• 0.24.4
• 0.24.5
• 0.24.6
• 0.24.7
• 0.24.8
• 0.24.9
• 0.24.10

License

• open-source

Website

• Product: https://github.com/nanomq/nanomq/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion