Live › vulnerability › CVE-2026-114550
libwebsockets mishandles incoming MQTT PUBACK packets and writes past the end of an allocated buffer. A remote attacker who sends a crafted packet can execute arbitrary code in the context of the affected process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-04 00:46 UTC. All times on this page are UTC.
Applications and devices that use libwebsockets with its MQTT role enabled and process MQTT PUBACK packets from a peer (client talking to a broker, or any MQTT traffic an attacker can inject) are exposed. Look at IoT gateways, embedded firmware and C services that bundle libwebsockets. Builds without MQTT support, or that never connect to untrusted MQTT peers, can skip it. The affected version range is not stated by the sources.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
libwebsockets MQTT Protocol PUBACK Packet Handling Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of libwebsockets. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the handling of PUBACK packets. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-31039.
This page as .md · .json · in your agent: get_signal("CVE-2026-114550")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.