CVE-2026-54412: CWE-125 Out-of-bounds Read in LiamBindle MQTT-C
LiamBindle MQTT-C versions up to 1.1.6 contain a heap-based out-of-bounds read and integer underflow vulnerability in the mqtt_unpack_publish_response() function. This flaw 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 crafted PUBLISH packet. The vulnerability arises from improper validation of the topic_name_size field relative to the remaining packet length, leading to an out-of-bounds read and a large memmove() operation that crashes the process.
AI Analysis
Technical Summary
CVE-2026-54412 is a heap-based out-of-bounds read and integer underflow vulnerability in LiamBindle MQTT-C through version 1.1.6. The mqtt_unpack_publish_response() function validates only that the fixed-header remaining_length is at least 4, then reads a 16-bit topic_name_size from the broker-controlled packet. It advances the parse pointer by topic_name_size without verifying that topic_name_size plus overhead fits within remaining_length. It then calculates application_message_size as remaining_length minus topic_name_size minus 2 or 4, using unsigned arithmetic, causing an integer underflow. This underflow leads to a memmove() with an excessively large size, causing a crash and potential disclosure of adjacent heap memory. An attacker can trigger this by sending a crafted PUBLISH packet with topic_name_size set to 0xFFFF and remaining_length set to 7.
Potential Impact
A remote unauthenticated attacker who controls an MQTT broker or can inject MQTT traffic into an unencrypted session can crash the MQTT-C client and potentially read adjacent heap memory. This can lead to denial of service and information disclosure. The vulnerability does not require authentication and can be triggered remotely via network access to the MQTT client.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, avoid using MQTT-C in unencrypted sessions or with untrusted MQTT brokers to reduce exposure. Monitor vendor communications for updates on remediation.
CVE-2026-54412: CWE-125 Out-of-bounds Read in LiamBindle MQTT-C
Description
LiamBindle MQTT-C versions up to 1.1.6 contain a heap-based out-of-bounds read and integer underflow vulnerability in the mqtt_unpack_publish_response() function. This flaw 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 crafted PUBLISH packet. The vulnerability arises from improper validation of the topic_name_size field relative to the remaining packet length, leading to an out-of-bounds read and a large memmove() operation that crashes the process.
CVSS v4.0
Score 7.8high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-54412 is a heap-based out-of-bounds read and integer underflow vulnerability in LiamBindle MQTT-C through version 1.1.6. The mqtt_unpack_publish_response() function validates only that the fixed-header remaining_length is at least 4, then reads a 16-bit topic_name_size from the broker-controlled packet. It advances the parse pointer by topic_name_size without verifying that topic_name_size plus overhead fits within remaining_length. It then calculates application_message_size as remaining_length minus topic_name_size minus 2 or 4, using unsigned arithmetic, causing an integer underflow. This underflow leads to a memmove() with an excessively large size, causing a crash and potential disclosure of adjacent heap memory. An attacker can trigger this by sending a crafted PUBLISH packet with topic_name_size set to 0xFFFF and remaining_length set to 7.
Potential Impact
A remote unauthenticated attacker who controls an MQTT broker or can inject MQTT traffic into an unencrypted session can crash the MQTT-C client and potentially read adjacent heap memory. This can lead to denial of service and information disclosure. The vulnerability does not require authentication and can be triggered remotely via network access to the MQTT client.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, avoid using MQTT-C in unencrypted sessions or with untrusted MQTT brokers to reduce exposure. Monitor vendor communications for updates on remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TuranSec
- Date Reserved
- 2026-06-13T16:39:46.122Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2eee6be617e2d834ca6d33
Added to database: 06/14/2026, 18:09:47 UTC
Last enriched: 06/22/2026, 15:19:15 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 123
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.