{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-63341","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-07-16T14:14:24.385Z","datePublished":"2026-10-30T22:09:50.280Z","dateUpdated":"2026-10-30T22:09:50.280Z"},"containers":{"cna":{"title":"Aedes has Uncaught Exception and Uncontrolled Resource Consumption","problemTypes":[{"descriptions":[{"cweId":"CWE-248","lang":"en","description":"CWE-248: Uncaught Exception","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-400","lang":"en","description":"CWE-400: Uncontrolled Resource Consumption","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"references":[{"name":"https://github.com/moscajs/aedes/security/advisories/GHSA-xxqp-5qx8-gj5q","tags":["x_refsource_CONFIRM"],"url":"https://github.com/moscajs/aedes/security/advisories/GHSA-xxqp-5qx8-gj5q"},{"name":"https://github.com/moscajs/aedes/commit/b9024faa4cb416c4c6980760b4d7f55336315f2d","tags":["x_refsource_MISC"],"url":"https://github.com/moscajs/aedes/commit/b9024faa4cb416c4c6980760b4d7f55336315f2d"},{"name":"https://github.com/moscajs/aedes/releases/tag/v1.1.1","tags":["x_refsource_MISC"],"url":"https://github.com/moscajs/aedes/releases/tag/v1.1.1"}],"affected":[{"vendor":"moscajs","product":"aedes","versions":[{"version":"< 1.1.1","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-10-30T22:09:50.280Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-xxqp-5qx8-gj5q","discovery":"UNKNOWN"}}}}