Aedes is an MQTT broker that can run on any stream server. Prior to 1.1.1, the MQTT broker does not bound topic depth or structural complexity before passing topics through `mqemitter` into `qlobber`. A `PUBLISH`, `SUBSCRIBE`, or registered `Will` message containing an excessively deep topic can reach `qlobber._split_words` in `lib/qlobber.js` and trigger an uncaught `too many words` exception. Calls from `handlers/subscribe.js` and the publishing logic are not protected against that exception, so it escapes to the `Node.js event loop` and terminates the entire broker. The `Will` path is independently reachable when a client disconnects ungracefully: it calls `broker.publish` directly and bypasses the `PUBLISH` handler. An attacker must be able to establish an `MQTT session`, authenticated or unauthenticated according to broker configuration. A successful attack disconnects all legitimate clients and prevents reconnection until the broker process restarts. This issue is fixed in version 1.1.1.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 7.5 · moscajsNVD modified 2026-10-30 22:09
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 3
- https://github.com/moscajs/aedes/security/advisories/GHSA-xxqp-5qx8-gj5q x_refsource_confirm
- https://github.com/moscajs/aedes/commit/b9024faa4cb416c4c6980760b4d7f55336315f2d x_refsource_misc
- https://github.com/moscajs/aedes/releases/tag/v1.1.1 x_refsource_misc