CVE-2025-66023: NanoMQ has Use-After-Free of malformed bridging message
NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Versions prior to 0.24.5 have a Heap-Use-After-Free (UAF) vulnerability within the MQTT bridge client component (implemented via the underlying NanoNNG library). The vulnerability is triggered when NanoMQ acts as a bridge connecting to a remote MQTT broker. A malicious remote broker can trigger a crash (Denial of Service) or potential memory corruption by accepting the connection and immediately sending a malformed packet sequence. Version 0.34.5 contains a patch. The patch enforces stricter protocol adherence in the MQTT client SDK embedded in NanoMQ. Specifically, it ensures that CONNACK is always the first packet processed in the line. This prevents the state confusion that led to the Heap-Use-After-Free (UAF) when a malicious server sent a malformed packet sequence immediately after connection establishment. As a workaround, validate the remote broker before bridging.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66023?
CVE-2025-66023 is classified as high severity due to its Heap-Use-After-Free vulnerability.
How do I fix CVE-2025-66023?
To fix CVE-2025-66023, upgrade to NanoMQ version 0.24.5 or later.
What components are affected by CVE-2025-66023?
CVE-2025-66023 affects the MQTT bridge client component of NanoMQ.
What versions of NanoMQ are impacted by CVE-2025-66023?
CVE-2025-66023 impacts all versions of NanoMQ prior to 0.24.5.
What can be exploited in CVE-2025-66023?
The Heap-Use-After-Free vulnerability in CVE-2025-66023 can be exploited to potentially execute arbitrary code.