CVE-2026-129705

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

GHSA-m6rg-rrm7-h727 ↗EUVD-2026-128522 ↗

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-290 Authentication Bypass by Spoofing
ETK-2026-4786Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss0.1ethiack provisional
9h 42msince last run
1h 22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h04m
0
+4h
+6h
+8h
+10h
+12h

description

Eclipse Mosquitto 2.1.0 through 2.1.2 can accept falsified SSL-related connection information on listeners configured for PROXY protocol v2. An attacker must be able to connect through, or impersonate, an untrusted proxy to such a listener.

mitigation

Restrict each PROXY protocol v2 listener so that only trusted proxy addresses can connect, and block all direct client access to it. Use network controls or listener access rules to enforce this separation.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 10:07Z
Δ 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:07Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4786",
  "cve_id": "CVE-2026-129705",
  "display_id": "CVE-2026-129705",
  "ghsa_id": "GHSA-m6rg-rrm7-h727",
  "euvd_id": "EUVD-2026-128522",
  "status": "published",
  "anchor_state": "anchored",
  "title": "PROXY protocol SSL identity spoofing in Eclipse Mosquitto",
  "summary": "Eclipse Mosquitto 2.1.0 through 2.1.2 can accept falsified SSL-related connection information on listeners configured for PROXY protocol v2. An attacker must be able to connect through, or impersonate, an untrusted proxy to such a listener.",
  "mitigation": "Restrict each PROXY protocol v2 listener so that only trusted proxy addresses can connect, and block all direct client access to it. Use network controls or listener access rules to enforce this separation.",
  "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": [
    290
  ],
  "cvss_score": 0.1,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 81.73546506666666,
  "t0_at": "2026-11-18T10:07:32.743000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T10:07:32.743000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T10:07:32.743000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-129705"
    }
  }
}

published 2026-11-18 10:49Z
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.