Skip to main content
VulnerabilityPublished

CVE-2026-63341: Aedes has Uncaught Exception and Uncontrolled Resource Consumption

Affects aedesSource GCVE Database

0
Compare
Authoritative record:CVE-2026-63341· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.1.1 soon.

Data as of 21 Nov 2026, 00:31 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 1.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade aedes to 1.1.1.

Affected software

ProductAffectedFixed in
npmaedesAffected
  • <1.1.1
Fixed in
  • 1.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Aedes version 1.1.1. Users should upgrade to version 1.1.1 or later to remediate this vulnerability. Until upgraded, consider implementing perimeter controls to restrict untrusted clients from sending deeply nested topic strings. No other vendor advisory mitigation instructions are provided.

Description

Aedes MQTT broker versions prior to 1.1.1 contain a remote denial of service vulnerability. An attacker can cause the broker process to crash by sending MQTT messages with excessively recursive topic strings, triggering an uncaught exception in an internal routing library. This occurs due to lack of input validation and error handling for deeply nested topic strings. The vulnerability affects all stable versions before 1.1.1 and is fixed in version 1.1.1.

References

Community reviews

Loading reviews…