Skip to main content
Menu
CVEs

CVE

Eclipse Mosquitto auth bypass in PBKDF2 password hashing

CVE-2026-126708Published Updated Summary written by a model

Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Eclipse Mosquitto does not check whether its sha512-pbkdf2 and legacy sha512 password hashing succeeded. When it runs with OpenSSL 4.0's FIPS provider, newly created passwords shorter than 8 characters can be matched by any other password shorter than 8 characters, so an attacker can log in without knowing the real password.

Original description

In Eclipse Mosquitto versions 2.0.0 to 2.0.22 and 2.1.0 to 2.1.2, the return value of password hash functions for sha512-pbkdf2 and legacy sha512 were not checked. Starting with OpenSSL 4.0, sha512-pbkdf2 hashing will fail when using the FIPS provider for passwords shorter than 8 characters. This has the effect that newly created passwords would match against any other password with fewer than 8 characters.

cve.now Index

5Pcve.now Index 5 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126708 (Unchecked PKCS5_PBKDF2_HMAC() return can authenticate any password), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126708 (entry last updated 2026-11-18):
Affected:
- Eclipse Foundation Eclipse Mosquitto: from 2.0.0, through 2.0.22; from 2.1.0, through 2.1.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126708 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126708 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-mosquitto/mosquitto/security/advisories/GHSA-878w-672v-qwmf
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/567
- http://www.openwall.com/lists/oss-security/2026/11/17/16
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126708
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126708"}.

Timeline

  1. CVE published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • Eclipse Foundation Eclipse Mosquitto

    From 2.0.0 · through 2.0.22; From 2.1.0 · through 2.1.2

Evidence 5

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · eclipse-mosquitto/mosquitto · Advisory GHSA-878w-672v-qwmf
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/567
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-126708
RecordNVD · CVE-2026-126708
Write-ups 1Establishes: Technical detail and context.
Linkopenwall.com · lists/oss-security/2026/11/17/16

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126708

Is CVE-2026-126708 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-126708?

Eclipse Mosquitto: from 2.0.0 through 2.0.22; from 2.1.0 through 2.1.2.Source: cve.now feed data

More CVEs