cve.bz

CVE-2026-114550 libwebsockets libwebsockets: Out-of-bounds Write

8.1 highEPSS 0.8%

High (8.1) in libwebsockets libwebsockets. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

8.1 high
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-114550 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114550?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114550?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114550 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
libwebsocketsb4b5aed3903eaff09cd76a410f69bbe5dff66f8e

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libwebsocketsno fix listedDEBIAN-CVE-2026-114550
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 morelibwebsocketsno fix listedUBUNTU-CVE-2026-114550

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

libwebsockets MQTT PUBACK packet handler performs an out-of-bounds write due to incorrect parser-state transition on the property-length VBI; remote unauthenticated attackers who can reach an MQTT-enabled lws endpoint may achieve arbitrary code execution; fixed upstream in commit c9e8e18; CVSS 8.1 IMPORTANT consistent with ZDI-26-792

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-04) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to correct parser state transitions during MQTT PUBACK packet property length processing in libwebsockets: upgrade to the fixed Libwebsockets builds, which transition the MQTT parser state to LMQCPP_EAT_PROPERTIES_AND_COMPLETE instead of LMQCPP_PUBACK_VH_PKT_ID and remove variable byte integer tracking re-initialization, closing crafted MQTT PUBACK packets. Until patched, this is a concern on applications utilizing libwebsockets MQTT protocol handling exposed to network access, so restrict network access to applications exposing libwebsockets MQTT endpoints so unauthenticated external traffic cannot reach the parser. As a compensating measure, Randomize memory layout using ASLR to prevent reliable code execution via the out-of-bounds memory write, Enable Full RELRO and PIE to prevent Global Offset Table overwrites and enforce position-independent execution, and Implement Control Flow Integrity or Shadow Call Stack to restrict indirect branch targets and protect return addresses against ROP and JOP payloads. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds write defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)

ProductPackageStateAdvisory
A-MQ Interconnect 1libwebsocketsAffected
Red Hat OpenStack Platform 16.2libwebsocketsAffected
Red Hat OpenStack Platform 17.1libwebsocketsAffected
Red Hat Service Interconnect 2libwebsocketsAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114550.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-114550 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-114550 / ZDI-CAN-31039: libwebsockets MQTT PUBACK OOB write PoC lab (podman)

References

Check your stackJSON