CVE-2026-54412
LiamBindle MQTT-C through version 1.1.6 contains a heap-based …
LiamBindle MQTT-C through version 1.1.6 contains a heap-based out-of-bounds read and integer underflow in the mqtt_unpack_publish_response() function in src/mqtt.c that allows a remote unauthenticated attacker controlling an MQTT broker - or able to inject MQTT traffic into an unencrypted session - to crash a subscribed MQTT-C client and potentially disclose adjacent heap memory by sending a single crafted PUBLISH packet. The function validates only that the fixed-header remaining_length is at least 4, then reads the 16-bit topic_name_size field from the broker-controlled packet and advances the parse pointer by that value without verifying that topic_name_size plus the surrounding overhead fits within remaining_length; it subsequently computes application_message_size as remaining_length - topic_name_size - 2 (QoS 0) or - 4 (QoS greater than 0) in unsigned arithmetic, producing an integer underflow that is then passed to memmove(). A PUBLISH packet with topic_name_size = 0xFFFF and remaining_length = 7 advances the parse pointer 65535 bytes past the receive buffer (out-of-bounds read) and causes an application_message_size near 2^32, crashing the process when the resulting memmove() is executed.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- cwe.mitre.org/data/definitions/125.html
- cwe.mitre.org/data/definitions/191.html
- github.com/LiamBindle/MQTT-C
- github.com/LiamBindle/MQTT-C/blob/v1.1.6/src/mqtt.c#L1334
- github.com/LiamBindle/MQTT-C/pull/208
- github.com/LiamBindle/MQTT-C/releases/tag/v1.1.7
- nvd.nist.gov/vuln/detail/CVE-2026-54412
- cve.org/CVERecord?id=CVE-2026-54412
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.