CVE-2026-110486

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

GHSA-6j8m-r32v-4h38 ↗EUVD-2026-128524 ↗

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.
Eclipse Foundation Eclipse Mosquitto 2.1.0-2.1.2
fixed in 2.1.3
CWE-787 Out-of-bounds Write
ETK-2026-4784Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 39msince last run
1h 01mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h12m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Eclipse Mosquitto 2.1 through 2.1.2 is affected when it exposes a listener using WebSockets. A remote client able to connect to that listener can disclose broker-process memory, crash the broker, or potentially run code as the broker account, including where anonymous MQTT access is disabled.

mitigation

Upgrade Mosquitto to 2.1.4. Until upgraded, disable WebSocket listeners or restrict network access to them to trusted clients.

fixed in 2.1.3

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
1h 01m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 10:15Z
Δ 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-11-18 10:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4784",
  "cve_id": "CVE-2026-110486",
  "display_id": "CVE-2026-110486",
  "ghsa_id": "GHSA-6j8m-r32v-4h38",
  "euvd_id": "EUVD-2026-128524",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Eclipse Mosquitto WebSocket heap memory corruption",
  "summary": "Eclipse Mosquitto 2.1 through 2.1.2 is affected when it exposes a listener using WebSockets. A remote client able to connect to that listener can disclose broker-process memory, crash the broker, or potentially run code as the broker account, including where anonymous MQTT access is disabled.",
  "mitigation": "Upgrade Mosquitto to 2.1.4. Until upgraded, disable WebSocket listeners or restrict network access to them to trusted clients.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Mosquitto",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.1.0-2.1.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "2.1.3"
      ],
      "package_name": "Mosquitto",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 61.270536,
  "t0_at": "2026-11-18T10:15:09.085000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T10:15:09.085000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T10:15:09.085000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110486"
    }
  }
}

published 2026-11-18 10:25Z
last change 2026-11-18 21:43Z

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.