External risk intelligence

Eclipse Mosquitto WebSocket Heap Corruption and Information Disclosure

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-110486

Eclipse Mosquitto is a widely deployed MQTT broker. When configured with WebSocket listeners, it is designed to facilitate communication with remote clients, often across network boundaries or over the public internet to support IoT and messaging applications. The vulnerability is reachable via unauthenticated packets, making it accessible to any remote entity capable of connecting to the broker's listener.

Out-of-bounds Write

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Eclipse Mosquitto, a popular MQTT broker, could allow unauthenticated remote attackers to disclose sensitive information and potentially execute code. This issue stems from how the software handles specific WebSocket data frames, leading to memory corruption that can be exploited to crash the service or gain control.

  • Malicious actors can crash or control the broker.
  • Affects widely deployed IoT and messaging infrastructure.
  • Confirm relevance and exposure of Mosquitto deployments.

Attack Path

How an attacker could exploit the issue

An attacker can target a Mosquitto broker configured for WebSocket communication. By sending specially crafted, empty WebSocket data frames, the attacker can trick the broker into misinterpreting packet lengths, leading to memory corruption. This can result in sensitive information being exposed from the broker's memory or an out-of-bounds write, potentially allowing the attacker to execute code as the broker's user.

  • Unauthenticated clients can connect.
  • Empty WebSocket frames trigger errors.
  • Heap corruption and code execution.

Live Threat

Current exploitation, exposure, and threat context

When configured with WebSocket listeners, this vulnerability could affect the broker by exposing uninitialized heap memory containing sensitive pointers, and allow an attacker to write past allocated buffers. This may lead to the broker crashing or potentially allow for remote code execution when supported by the advisory.

  • Broker memory could be exposed.
  • Attacker sends specially crafted WebSocket frames.
  • Remote code execution or denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Eclipse Mosquitto affects MQTT brokers configured with WebSocket listeners. Given its wide deployment for IoT and messaging applications, and its remote, unauthenticated exploitability, both infrastructure and security teams are likely involved in the response. The immediate priority is to identify all instances of the affected Mosquitto broker, assess their exposure and business criticality, and then coordinate remediation efforts, potentially involving vendor engagement and careful planning around maintenance windows.

  • Identify Mosquitto broker instances.
  • Verify WebSocket listener exposure.
  • Plan remediation and coordinate vendor.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Eclipse Mosquitto?

Eclipse Mosquitto is a lightweight message broker that implements the MQTT protocol. It is commonly used in IoT and messaging systems to facilitate communication between devices and applications. By managing message routing and subscriptions, it acts as a central hub where clients exchange data. This vulnerability specifically affects how it manages WebSocket connections, which are often used to bridge these messages into web-based environments.

How does CVE-2026-110486 create a security risk?

This vulnerability involves memory handling errors, specifically improper input validation (CWE-908) and out-of-bounds access (CWE-191 and CWE-787). Because the broker misinterprets empty WebSocket data frames, it can mistakenly expose sensitive uninitialized memory—including system pointers—and allow an attacker to write data into memory areas they should not access. This combination of leaking information and corrupting memory is what enables more severe outcomes like remote code execution.

When does this vulnerability trigger?

The issue is triggered when a Mosquitto broker is configured with a WebSocket listener and receives a specially crafted, empty WebSocket data frame. It is important to note that this happens before any authentication occurs; even if you have configured 'allow_anonymous false', the broker is still vulnerable because it processes these malicious frames during the initial connection phase. Non-WebSocket traffic remains unaffected by this specific flaw.

Do I need to worry if my Mosquitto broker is internal?

Yes, you should still evaluate your risk. According to Halo Surface Signal, this vulnerability is reachable by any remote entity that can establish a connection to your broker's WebSocket listener. While internet-facing brokers are at the highest risk, any device or application within your internal network that can reach the broker's listener can potentially exploit this. You should confirm if your listeners are accessible beyond intended boundaries.

What should I do to address this CVE?

The first step is to create an inventory of all your Mosquitto broker instances and verify which ones have WebSocket listeners enabled. Once you have identified your footprint, assess the criticality of those specific services to your operations. Prioritize these systems for patching or configuration updates, and coordinate with your technical teams to schedule the necessary maintenance or software upgrades to remediate the vulnerability.

References