CVE-2026-126708

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

GHSA-878w-672v-qwmf ↗EUVD-2026-128521 ↗

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.0.0-2.0.22; 2.1.0-2.1.2
fixed in 2.0.23, 2.1.3
CWE-252 Unchecked Return Value
ETK-2026-4785Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.0ethiack provisional
9h 56msince 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+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

Eclipse Mosquitto 2.0.0 through 2.0.22 and 2.1.0 through 2.1.2 can mishandle failures from certain SHA-512 password-hashing modes. An attacker may authenticate using a different password shorter than eight characters when an affected account was newly created with a short password and Mosquitto uses the OpenSSL 4 FIPS provider.

mitigation

Upgrade Mosquitto to 2.0.23, 2.1.3 or later.

fixed in 2.0.23, 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.
contextual
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 09:59Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-18 09:59Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4785",
  "cve_id": "CVE-2026-126708",
  "display_id": "CVE-2026-126708",
  "ghsa_id": "GHSA-878w-672v-qwmf",
  "euvd_id": "EUVD-2026-128521",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unchecked password-hash failures in Eclipse Mosquitto",
  "summary": "Eclipse Mosquitto 2.0.0 through 2.0.22 and 2.1.0 through 2.1.2 can mishandle failures from certain SHA-512 password-hashing modes. An attacker may authenticate using a different password shorter than eight characters when an affected account was newly created with a short password and Mosquitto uses the OpenSSL 4 FIPS provider.",
  "mitigation": "Upgrade Mosquitto to 2.0.23, 2.1.3 or later.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Mosquitto",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.0.0-2.0.22",
        "2.1.0-2.1.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "2.0.23",
        "2.1.3"
      ],
      "package_name": "Mosquitto",
      "purl": null
    }
  ],
  "cwes": [
    252
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 81.69351605,
  "t0_at": "2026-11-18T09:59:24.842000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T09:59:24.842000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T09:59:24.842000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126708"
    }
  }
}

published 2026-11-18 10:36Z
last change 2026-11-18 21:29Z

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.