Skip to content
Threat Brief

← All advisories

CVE-2026-110486

Critical 9.8No known exploitationFix status unknown

Remote heap out-of-bounds read/write in Eclipse Mosquitto

Record last updated

CVSS score

9.8

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

1.0%

Higher than 65% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session.

Weakness: CWE-787, CWE-908, CWE-191

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
Eclipse FoundationEclipse Mosquittofrom 2.1 up to and including 2.1.2Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by eclipse

    Source: CVE Program (opens in a new tab)

Vendor guidance and references