CVE-2026-63341

waiting for further signalsZero needs more public information before it can validate it.

GHSA-xxqp-5qx8-gj5q ↗EUVD-2026-114567 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
moscajs aedes <= 1.1.0
fixed in 1.1.1
CWE-248 Uncaught Exception
ETK-2026-3125Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/aedes
3h 21msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h18m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Aedes versions before 1.1.1 can terminate when processing MQTT messages with excessively complex topic structures. An attacker who can establish an MQTT session may disconnect clients and prevent new connections until the broker is restarted.

mitigation

Upgrade the aedes package to version 1.1.1 or later. Until upgraded, restrict MQTT session access to trusted clients and restart affected broker processes if they terminate.

fixed in 1.1.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 22:09Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-30 22:09Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-63341

{
  "etk_id": "ETK-2026-3125",
  "cve_id": "CVE-2026-63341",
  "display_id": "CVE-2026-63341",
  "ghsa_id": "GHSA-xxqp-5qx8-gj5q",
  "euvd_id": "EUVD-2026-114567",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncaught topic-processing exception in Aedes MQTT broker",
  "summary": "Aedes versions before 1.1.1 can terminate when processing MQTT messages with excessively complex topic structures. An attacker who can establish an MQTT session may disconnect clients and prevent new connections until the broker is restarted.",
  "mitigation": "Upgrade the aedes package to version 1.1.1 or later. Until upgraded, restrict MQTT session access to trusted clients and restart affected broker processes if they terminate.",
  "vendor": "moscajs",
  "product": "aedes",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.1.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.1.1"
      ],
      "package_name": "aedes",
      "purl": "pkg:npm/aedes"
    }
  ],
  "cwes": [
    248
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.3036182,
  "t0_at": "2026-10-30T22:09:50.280000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T22:09:50.280000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T22:09:50.280000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63341"
    }
  }
}

published 2026-10-30 23:07Z
last change 2026-10-31 01:48Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.